As part of a disaster recovery test of our TFS 2008 instance I hoped to restore our backups of the database (currently on SQL Server 2005) to SQL Server 2008.
I noticed a warning on MSDN that this could make a restore impossible.
Has this been done in the wild? What are the risks?
Your disaster recovery plan should never include an upgrade at the same time. It's prudent to make the upgrade first and then plan your disaster recovery plan. Waiting for a recovery opportunity could spell trouble.
That being said, as long as you're using the latest service packs, TFS 2008 is fully supported on SQL Server 2008 now.
Buck Hodges is a definitive TFS guru. Here's what he says:
SQL 2008 SP1 has just been released,
and we've gotten a couple of questions
about whether it is supported with
with Team Foundation Server 2008. We
tested SQL 2008 SP1 with both the
original release of TFS 2008 and TFS
2008 SP1, and we do fully support
using it with either release of TFS
2008.
http://blogs.msdn.com/buckh/archive/2009/04/09/tfs-2008-supports-sql-2008-sp1.aspx
I have performed one upgrade of TFS 2008, and we tried to restore backups to a SQL Server 2008 instance. We were also upgrading from the final beta of TFS 2008, so I can't say whether the issues we encountered were due to it being from a beta, or if it was due to the change in SQL Server versions. It turned into a minor disaster, and we ended up reinstalling TFS fresh and copied our source code into it (which luckily was fully checked out on several developer machines). We lost our source control history for a short time, but we were eventually able to get the original instance up and running again, which we kept around for legacy source control history reference.
Related
I'm a beginner in this, I've been searching for long on internet. But as many solution in internet, I don't understand as much i wanted. And I have some question to for resolution. I see a place the recommend to ask some like this as Super User, but I recently just started using 'Stack Overflow' so I don't know How To Use Super User.
Start when I download a new setup of SQL Server 2016 and choose option to 'Upgrade-from-previous-version', from process I see, it just added 2 features.
From what I really want is to change entirely my SQL server from 2014 to 2016.
Two Server in services.msc
So i try to do option 'basic-installation' from installer and it work honestly but provide 2 server which server 2016 and 2014.
Maybe I can just uninstall the server 2014, and get work with 2016 instead. But Can I bring my database in 2014 too?, I mean it has compatibility-problem.
And it don't have SQL Server Management Studio so I download a newest version of it (v18.00)
Two server with different SQL Server version
My question is =
Can I keep my database in server 2014, my database in 2016 is empty (did I must attach it again)?
Did it just OK to have two Microsoft SQL Server Management Studio?
Why I don't get MSSMS when I install SQL Server 2016?
If I must do Question1, How To Upgrade my database to version 2016?
Is it bad for my laptop to having two Version of SQL Server, or I must delete one?
Backup and restore to 2016 (or keep it in 2014)
Yes, but not necessary, just use latest version, uninstall older
Management Studio can be downloaded separately
See (1)
No, both can be kept, but remember that both services will be running which may impact performance and resource usage. You can stop these services using SQL Server Configuration Manager
Our current Reporting and analysis server for TFS 2015 is SQL 2012 Standard. I would like to upgrade to SQL 2016 Enterprise (Join our current 2016 Enterprise environment). What would that process be and will there be any historical data loss?
Is it as simple as remove the configuration for Standard and the point it to the new Enterprise server and then let it rebuild the warehouse and the cube?
outside of the time it takes to rebuild, will I loose anything?
First, check your versions.
TFS 2015 RTM does not support SQL Server 2016.
TFS 2015 Update 3 and beyond does support SQL Server 2016.
Assuming your reporting databases (TFS_Analysis and TFS_Warehouse) are on a totally separate instance of SQL server than your TFS operational databases (TFS_Configuration and TFS_<ProjectCollection>), or are going to be moved to a totally separate database instance, there should be minimal risk. You just update the reporting configuration to point to the new SSRS/SSAS servers and databases and everything will rebuild, no historical data will be lost.
If your intent is to totally migrate your TFS databases to a new SQL server version, it's a more involved process with a higher degree of risk -- downtime will be required and it's wise to do a test migration first.
Regardless, no data will be lost.
What is the best (or THE) way to change my SQL Express 2008 (with advance...) installation to a 2008 Developer edition?
I need to keep the databases, along with the logins and so on.
I need to upgrade because, I Want to use all the features in TFS 2010.
Do I have to make backups of all the data and uninstall express - install developer?
Is there a quicker way?
SOLVED:
In the SQL Server Installation Center, there a Edition Upgrade options found under Maintenance. The only thing is that you have to choose processor type as x86 (as Express is only x86) in the options in the Installation Center. Now my SQL Server is developer.
We had to do the same thing at one time. I think we simply backed up our database(s) and the master and msdb databases as a precaution, to restore if we had to, which I don't think we did.
I am told that SQL Server 2005 installation with BI tools and SQL Server 2008 with BI tools can't work together on the same computer. Apparently "some" things stop working. This was told to me by one of my team members. Since I'm new to SQL BI, I cant discount what he has said altogether and I dont want to install them both on my dev box and find out later that there is problem.
Has anyone here installed them both, used both sufficiently well and found it to be working fine?
Thanks.
I have a complete install of both SQL2005 developer and SQL2008 developer on my workstation. Nothing unusual has happened. A collegue also has both installed and is making use of the BI side of SQL 2005, again we haven't noticed any ill affects.
Server side I would think twice before installing both, but only becuase of resource usasge. If your box has sufficent resources available then I wouldn't expect any issue.
I'm not sure if this is your development system or the server... If its the server you can have side by side reporting services on the same server at the same time (though you use double the resources too). I am not sure why you would though; the reporting services 2008 is vastly superior and can report on data from the sql 2005 instance. If you are worried about the lack of a service pack for sql 2008 you can report on data in sql 2008 from reporting services 2005 (http://msdn.microsoft.com/en-us/library/ms143736.aspx)
If its local on your own pc you can have the development tools both installed at the same time (http://msdn.microsoft.com/en-us/library/bb500441.aspx); though in this case i would use the sql 2005 tools only if you are migrating to sql 2008 as SQL 2005 code works on 2008 but not necessarily the other way around.
If you have reporting services models make sure you check out report builder 2 which ms launched this week. Its a much better user experience than report builder 1.
We have a production web and database server with SQL Server 2000. (However, a few clients they have their own servers with SQL 2005.) So we have local installs of SQL 2005 Express for development on Windows XP SP3 boxes (which don't allow SQL 2000 Enterprise installations).
We often need to copy SQL 2000 databases to SQL 2005 instances. In the past, we have used the SQL Publishing tool (also mentioned here). However, one of our databases is so big that using that tool fails as it creates SQL scripts that get too large for Management Studio to handle them properly. Besides, it takes too long... :)
We would use the Copy Database Wizard included with SQL 2005, but our development machines run SQL 2005 Express which don't included SQL Server Agent, which is required for Copy Database Wizard to work. So, I guess our solution will be to upgrade our development installs with the full version of SQL 2005 (we have an MSDN subscription of course).
I was wondering what other solutions, if any, work well for you guys? (Besides complaining to the bosses to upgrade our production servers to 2005 or even 2008--which I've already tried.)
Back it up in SQL Server 2000 and then use the RESTORE WITH MOVE command into 2005 Express.