Our website is backed by a database written using SQL Server 2008 R2 Enterprise. I am in India working with an outsource org and the only thing they can get is SQL server 2014 developer edition, which supports the compression options that are used with 2008 r2 enterprise. I have verified on my box that I can install 2014 developer, attach the mdf of the 2008 r2 database which gets set to 2008 compatibility, launch our site and everything appears to work. But I am concerned about potential issues if the database behaves in an unexpected way in 2014. The biggest issue I've read about is if TSQL code is written against a server running in compatibility mode, that may not behave as expected after it is deployed to the server running the actual version being emulated. These guys aren't going to be doing any database work, just website work, so that part may be of no concern. With that in mind, what are potential issues that we might run into?
Going forward with MS SQL backups has never been an issue. 2005 backup restored on 2008, no problem.
Going backwards won't work. 2008 backup, restoring onto 2005, won't work.
Related
I have a production system which had installed SQL Server 2012, so this system has the Integration Services 11. Then we upgraded the system with SQL Server 2014, so the system had two Integration Services 11 & 12. Then we upgraded to SQL Server 2016, so the system has now three Integration Services 11, 12 & 13.
I done some research on the Internet and i realized that even we upgrade the SQL Server the integration services are installed side-by-side. This is also confirmed from SQL Server Management Console.
When i run DTEXEC on CMD get default version 11, this means that my DTSX packages inside the SSISB Catalog are running using the Integration Services 11 and not the latest one? If this is correct how can i change this to the newest one?
I was recently part of such discussion. It is important to understand SSIS Backward compatibility before.
Also, refer SSIS through its SQL Server Data Tools version, as most commonly people understand it in that way. You can link your thoughts with below mentioned details:
SQL Build# PackageFormatVersion Visual Studio Version(SSDT)
2005 9 2 2005
2008 10 3 2008
2008 R2 10.5 3 2008
2012 11 6 2010 or BI 2012
2014 12 8 2012 CTP2 or 2013
2016 13 8 2015
source: sqlstudies
From this microsoft document you'll understand which SSIS version is compatible with which SQL Server.
Briefly:
Target version of SQL Server Development environment for SSIS packages
2016 SSDT 2015
2014 SSDT 2015 or SSDT-BI 2013
2012 SSDT 2015 or SSDT-BI 2012
In simple words, SSDT 2015 is capable of deployment on any server from 2012 onwards, whereas 2012, 2013 are restrictive.
Beware that, if you open sql server 2012 dtsx in SSDT 2015, then you cannot go back to open it from SSDT-BI 2012.
If this is correct how can i change this to the newest one?
Hence, if you want to upgrade all your packages, open them through SSDT-2015, select deployment version(right click project -> properties -> Target Server Version).
you can read more about these changes here(MSSQLTips)
I think the previous answer provides some very useful information. However, I think I understand the misconception here:
First, there is NO benefit or advantage of "changing this to the newest one". Some people think that SSIS 2016 (11) is better than SSIS 2014 (10) or lower - the fact is that , with SSIS2012 nothing changed except addition of several new features and a new way to deploy items. You will not obtain any speed or performance enhancement. It's just that you get access to a few extra components.
Second, this will never fail because of my answer above. Firstly, SSIS is backward compatible (which is what Microsoft brags about - but honestly, why wouldn't it be?? it's the exact same product sold under different titles, why would it NOT be backward compatible). Secondly, your previous editions of SSIS are there for those like a few features (such as ActiveX) to run in compatibility mode. All in all, I think the question is answered by the fact that SSIS is backward compatible and that NOTHING has changed in the past 3 editions of the product (2012, 2014 and 2016 are nearly identical, and no performance or architectural changes exist between 2008/2008R2 and 2012+)
If you'd like more information, have a look at this link, which starts off by stating:
SQL Server 2014 Integration Services (SSIS) can co-exist side-by-side
with SQL Server 2008 Integration Services and SQL Server 2012
Integration Services.
Hello I have installed management studio 2005(x64) alse I have microsoft sql server 2012 in my pc. But cant connect server due to dont know server name. (if sql server 2008 express were in my pc, default servername would be "./sqlexpress")
How can I connect server in my own pc ? And also I wanted to know;
Should I use another management studio ? can there be a problem use ms2005 with sqlserver 2012 ? Do you recemmond other studio ? (with exp. reason please)
Thank you anyone who just feel to help.
At least one of them must be a named instance. So, open the SQL Server 2012 version of SQL Server Configuration Manager, and see what the services say (and make sure the one you want to connect to is started - you can right-click to do so). Mine are all named instances:
So, if I wanted to connect to the SQL Server 2008 SP3 instance, I would use any of the following to connect:
.\SQL2008SP3
LOCALHOST\SQL2008SP3
(local)\SQL2008SP3
YOURMACHINENAME\SQL2008SP3
127.0.0.1\SQL2008SP3
The exception is if the subtext has (MSSQLSERVER) - this is a default instance rather than a named instance. In that case you would just connect to YOURMACHINENAME or ..
Also, no, you should not use Management Studio 2005 to manage SQL Server 2012 instances. In fact I think the above Configuration Manager won't show your 2012 instance. So before you do anything, you should uninstall the 2005 version of Management Studio, and go get the 2012 SP2 version here:
http://www.microsoft.com/en-us/download/details.aspx?id=43351
Click Download, the file you want is SQLManagementStudio_x64_ENU.exe. The nice thing about this version in 2012 SP1 is that it's the first version of SSMS Express that is actually fully functional and license free. Previously you had to live with limitations like no SQL Server Agent management, well those restrictions are now all gone.
(When you instal the client tools, this should also give you a new version of Configuration Manager, if your previous installation of SQL Server 2012 did not provide that for some reason.)
I created my Database using SQL server 2008 R2.
Then tried to attach it using Visual C# Developer 2010.
It gives me an error. Attached is the screenshot
Thank you
Sun
To solve your problem you'll need to upgrade to SQL Server 2008. Express edition is fine, as long as the database is less than 4Gb in size.
I am going to pay for some classes to learn MS SQL server 2008.
To prepare for the classes, I need to install MS SQL server 2008 in my home PC so that
I can do some self-learning myself after each lesson.
I came a cross a PC store that got a few second-hand copies of SQL server 2008 and
as they (the shop keepers) said, if I bought a copy from them, they would give me a free copy of Crystal Report CD (version 9) to me as a gift.
I am new to both MS SQL server 2008 and Crsytal Report.
I don't know if Crystal Report 9 is compatible with MS SQL server 2008
Please advise and help.
Unless you are going to need Crystal Reports for this class or a class you are taking in the near future, or need some of the extra functionality of the full version SQL Server for your class (such as Replication), why not just use the free SQL Server Express Edition? Unless your class concerns administration of SQL Server, SQL Server Express should suit your purposes and be a lot cheaper.
CR9 should be compatible to some extent with MS SQLServer 2008 - even if the Crystal native drivers for MS SQLServer don't work (I would expect that they would), you should still be able to use ODBC drivers.
That said, unless the second-hand copies are extremely cheap, why not just download SQLServer Express for free, as suggested by the other posters?
I have been looking for a way to migrate and upgrade our TFS 2008 server to 2010 server preferably without losing any data.
I have been looking at the TFS Integration Platform
http://tfsintegration.codeplex.com/
and also Visual Studio 2010 TFS Upgrade Guide
vs2010upgradeguide.codeplex.com
Looking at the document TFS Integration Platform - Migration Guidance.xps using the first link, it seems to suggest that I could preserve all the data by first migrating the TFS 2008 from one server to the other and then upgrade the TFS 2008 to 2010.
Is this true?
Thank you,
Chen
Chen - We just went through this process a few weeks ago. While it's not a trivial matter it can be done. There is actually specific guidance for an upgrade with migration to new hardware in the TFS Install Guide. Take a look at the Scenario: Upgrading Team Foundation Server section and the sub-section named Checklist: In-Place or Migration Upgrade on One or More Servers.
The most challenging part of the exercise for us was the SharePoint setup/configuration, but if you follow the guide closely it should go fairly smoothly. This post may help with the SharePoint piece.
If the database is on its own box then you first need to upgrade to SQL 2008. Once that is done you can install TFS 2010 on a new server, select upgrade during the install and point it to the database server.
If the database is on the same box as TFS 2008 then you first need to backup all the databases and restore them on to the new box with SQL 2008. Then install TFS 2010, choose upgrade during the install and point it to the database server.
It should be. Migration of 2008 from one server to another is primarily a database exercise, but it can get tricky when you are initializing the Application Tier.
To be honest, I thought the TFS Integration Platform migration was providing guidance around moving from TFS 2005 to TFS 2008. My understanding was that TFS 2010 has an upgrade feature included in the wizard that should take care of most things for you. Thus far, I've only installed TFS 2008 from scratch and TFS 2010 from scratch-- I haven't yet tried that part of the wizard.
Another consideration is the database platform for your TFS 2008 instance. In our case, our 2008 is installed on MS SQL Server 2005, and TFS 2010 requires SQL Server 2008, so that's going to make our upgrade potentially a bit trickier.