We want to maintain our sql server scripts history. What is the solution? can we integrate SQL Server Management Studio 2008 with TFS 2010?
Sure, there is, a DB professional which is a project type in the visual studio, this type of project will maintain DB objects as separate files so it can be treated as normal C# or VB file, for version control.
SSMS is able to save sql files to SCCI compliant source control systems, such as TFS. Here is an article explaining how to achieve this.
However, this just saves sql files but doesn't assist in the versioning of the schema objects in your database. Should you need to do this, SQL Source Control, which we have developed at Red Gate, allows you to connect your SQL Server instance in SSMS to your back-end source control system, such as TFS.
How exactly does that integrate with SSMS??? You can still go behind the scenes with ssms and edit whatever you want, regardless of source control.
Related
One of our server crashed running TFS express for personal projects. We do have tfs database backups on network location but not sure what version it was.
Is there any possible way to identify tfs version from database backups ?
Check the extended property TFS_PRODUCT_VERSION of any collection database (e.g. Tfs_DefaultCollection) using SQL Management Studio; then lookup in What version of Team Foundation Server do I have?
TFS_SCHEMA_VERSION is a bit easier to read if you are familiar with internal Visual Studio versions.
TFS isn't installed client-side. On the client you use Team Explorer, which is part of Visual Studio. So the only version on the client-side that is with the Visual Studio version which you get from Help->About. This may give what you want.
The version is stored with the file version of the Microsoft.TeamFoundation.Server.dll file. Not sure if this is contained in backuplogs. You can also double check it.
Does anybody know if it's possible to move a TFS repository from SQL 2012 Express to SQL 2008R2?
Background:
At some point someone in our shop installed TFS to test it. This was done on a SQL 2012 Express.
Over time this installation has become our de facto source control system and contains history for 25+ different solutions.
Now our Sys Admin would really like to get rid of this 2012 Express edition. Which means we have to move it to our 2008R2 SQL production server.
No, as far as I know this is not officialy supported. SQL Server is backward compatible meaning you can go from 2008 to 2012. The other way around however is not supported.
By far the easiest solution would be to move to a regular SQL Server 2012 install. When you have a license for TFS, you also get a license for SQL Server Standard that you can use.
If that's not possible, you should contact Microsoft support. They have a script that you can use to migrate the data from one database to another. This can be done to run a downgrade but it's only supported if Microsoft helps you with it.
I have TFS 2010 on an existing server and want to move it to a new server. I would like to keep all of my collations intact and make the move as smooth as possible. I would also like to use the Power Tools backup/restore feature to do this. I have backups now in a network location so how can I reliably restore these onto my newly installed and patched TFS 2010 box (with no configuration)?
Moving a TFS instance to a new server is a delicate procedure. The TFS Configuration database contains a lot of URI's, service accounts and other important information.
You can quickly restore a TFS backup to the same server, without issues. To actually move to different hardware or a clean installation, follow the following (lengthy) procedure. You can use your existing backups.
+1 for #jessehouwing
But if you have the same URI's, you can do the following
After you back up TFS 2010 using TFS Power Tools 2011, then you restored the TFS 2010 back up to another SQL Server or instance, or restored in the original SQL Server which your TFS 2010 configured?
If you want backup TFS 2010 using TFS Power Tools and restore to the original SQL Server, please refer to the detailed steps in this article: http://myalmblog.com/2010/09/12/tfs-2010-power-tools-tfs-backup-and-restore-hands-on-lab/.
If you want to backup TFS 2010 and restore to another SQL Server or instance, after restore TFS 2010 database on the new SQL Server, you need to configure the new SQL Server for your TFS 2010, please refer to the detailed steps in this document: http://msdn.microsoft.com/en-us/library/ms252516.aspx.
I am using SQL Server as a database and TFS 2008 as Source and Version Control. When I create a object in database respectively I will create the object in TFS as a sql file.
I am facing problem like some developers creating object in Database but they are not updating the TFS with the same.
How do I maintain the TFS and Database in sync and if any differences are there, how can I find easily ?
I would propose to only allow developers to add and modify SQL scripts in your TFS system. Then use build automation to execute those scripts against a clean database. That way, you are always 100% sure you can reproduce your database model and content from the items you have stored in TFS.
Does anybody have any recommendations for managing database changes with Team System 2008 and Team Foundation Server 2008? I am a developer for my company and was hoping to achieve source control over the database stored procedures, triggers, tables etc... with TFS 2008.
We are currently using TFS 2008 to manage our source code for our .Net projects. We have Visual Studio Team System 2008 that contains the Architecture Edition, Database Edition, Development Edition and Test Edition. I am not really familiar with the capabilities of the Database Edition.
I really appreciate any recommendations.
Just to let you guys know we will be using this for source control over 2005 and 2008 sql server databases. Thanks.
We have been using DB Ghost for out database change management. It does a good job capturing the entire database. They have a recommended flow for starting out and getting your db in source control.
That said, if you already have Team Suite, I would recommend using the built in tools. Here is a link to the MSDN Getting Started type info for Team Edition Database.
Good luck, and congratulations on making the decision to version your database. It is a challenging process, but a very important one.
With the database edition you can easily import you database objects and add the objects into source control. When you develop your database, you can do that from within the database project and then deploy the changes to sql server.
See also the Database Guide from the Visual Studio ALM Rangers: http://vsdatabaseguide.codeplex.com/