Is it Possible to integrate sql server databases into visual studio team foundation server 2008 as all possible circumstances like build making, version control,publishing etc....
and pls make sure that if we integrate this in to a team project combined both code and db in a single project and i would like know how it is possible....?
Look at the Red Gate SQL Source Control product. Thats what we use to version our database in TFS.
Related
We are using Microsoft SQL Server Data Tools - Business Intelligence for Visual Studio 2012 for our SSIS Packages development. We would like to integrate this with Team Foundation Server Express edition since it is free.
Please let me know whether this integration possible at all? What will be other limitations?
Thanks!
SQL Server Data Tools is a feature in VS, while TFS is a server that provides features like source code management, reporting, ect. If Visual Studio 2012 is not installed, you need to install Team Explorer to work with TFS.
Regarding TFS Express limitation, you may check this case: Limitations & Features of TFS Express 2013
By the way, instead of TFS Express, you may consider using Visual Studio Team Service.
I'd like to take advantage of Visual Studio Online but I have been using Team Foundation Server on-premises and would like to migrate my data (version control, work items, test cases, and test results) to get my team started with our history. How do I do that?
The Team Foundation Server Integration Platform is available as a free platform for migrating/synchronizing data between TFS servers and with Visual Studio Online.
The ALM Rangers have an article in MSDN Magazine with a walkthrough: http://msdn.microsoft.com/en-us/magazine/jj130558.aspx
There are a couple of limitations from what I understand:
Takes some work to get up and going but the walkthrough helps out a lot
This tool does migrate test cases but you need to run the UpdateSharedSteps tool from the product team.
Not actively invested in as new features in Team Foundation Server and Visual Studio Online lights up
Another option is to build your own migration utility using the Team Foundation Server SDK. You can use the Client Object Model to read data from your TFS server and then write it to your Visual Studio Online account.
There is a free migration utility from migrating data from Team Foundation Server on-premises to Visual Studio Online available from OpsHub: http://aka.ms/OpsHubVSOMigrationUtility.
It allows you to migrate team project(s) from TFS 2010, TFS 2012, and TFS 2013 including the history of:
Version Control
Work Items
Test Cases
It handles the most common scenarios by making smart assumptions that are good for most scenarios. For those with more advanced scenarios, the OpsHub Integration Platform is commercially available and helps with synchronizations, custom business rules during migrations including customized process templates, and migration/integrating with other ALM platforms like IBM, Atlassian, HP, etc.
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.
Can I use TFS Client 2010 with TFS server 2008?
Or it is not recommended ...?
We seem to be doing OK with this exact setup. All of the team queries, documents, reports, builds and source control integration seem to be working just fine. Admittedly, we've only been in the 2010 environment (against TFS2008) for about a week now.
That said, I imagine if we were going to run into issues, we would have by now.
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/