I would like to know how do I completely remove all installation for SQL Server 2017 and revert to 2008 R2?
I have attempted update of service by point to 2008 R2 install but no luck.
There is no way to downgrade your SQL Server version. You must uninstall 2017 and install 2008R2.
If you want to keep the data, you need to export it in some flat files, because once attached to newer server version, a database is upgraded and cannot be attached to an older one. Even restoring a backup made with newer version is not possible. The other option you have is to install 2008R2 and use import/export wizard to copy the data from 2017 to 2008R2. After you transfered your data, you can uninstall the existing 2017 instance.
Related
One of our client wants to move from TFS 2013 to TFS 2018. We don't have much information about the current TFS setup at client's end.
Can anyone please guide with what questions we need to ask to client to get the information regarding the current TFS system setup before we start with upgrade process.
Also share if there is any process document regarding upgrading the TFS 2013 to TFS 2018.
Thanks in advance.
You need to confirm the real requirements first, need to upgrade or migrate?
Check if the current device, OS and software match the Requirements and compatibility for the upgrade/migration :
Client operating systems:
TFS 2018 Windows 10 (Professional,Enterprise) Version 1607 or greater
TFS 2013 Windows 8.1 (Basic, Professional, Enterprise) Windows 7
(minimum SP1) (Home Premium, Professional, Enterprise, Ultimate)
SQL Server:
TFS 2013 Update 4 - SQL Server 2014 or SQL Server 2012 (minimum SP1)
TFS 2018 - SQL Server 2017 or SQL Server 2016 (minimum SP1)
Upgrade is a full data transfer. You will have all data in the previous TFS.
As TFS 2018 only supports SQL Server 2017 and SQL Server 2016 (minimum SP1), upgrade SQL Server is necessary.
You need to go through article Upgrade your deployment to the latest version of TFS before doing upgrade. And follow the steps in article Upgrade scenario walkthrough for Team Foundation Server to upgrade your TFS. Summarize the steps here:
Prepare your environment. The first step is to check the system
requirements for TFS 2018. Upgrade SQL Server is necessary for your
scenario. Including SQL Server, you also need to check other system
requirements and prepare the environment.
Expect the best, prepare for the worst. You must have a complete and
consistent set of database backups in case something goes wrong.
Do the upgrade. Once the preparation is done, you'll need to install
the new version of TFS to get new binaries, and then run through the
upgrade wizard to upgrade your databases.
Configure new features. Depending on what version you upgraded from,
you may need to configure each team project to gain access to some
of the new features made available.
Below threads for your reference:
https://blogs.msdn.microsoft.com/rob/2016/12/22/upgrading-from-tfs-2013-to-tfs-2017/
TFS 2012 to TFS 2018 Migration/Upgrade Path
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.
I reinstalled SQL Server Management Studio in my computer, then I'm trying to restore all backups.
Unfortunately, I get an error when trying to open one.
What should I do?, How do I set the BackupDirectory in my Settings?
I just installed Sql Server Express 2012 Sp1, and problem solved
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.
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.