OverviewIn most projects we see that we are not able to track the database properly. If we have given permission to every developer to make some changes in the database then if anyone makes a small change then that can create a problem. Because there is no tracking in SQL Server (for Stored Procedures, Functions, Tables, login permissions and so on) like we have the View History option in TFS. So now in Visual Studio 2012 or 2013 we have a feature to create a SQL project and we can track the changes for a specific Stored Procedure, function and so on. So updating directly in SQL Server can create a problem in a large application and be difficult to track. So instead of updating in SQL Server now we need to update in SQL Server from TFS. So that the DB Administrator or whoever handles DB can keep track properly of who has done a change and what the change is and for even any wrong change can be reverted.Procedure to create the project and keep track.
Now if we update the SQL Server from TFS and then we will check in that specific Stored Procedure in our Local TFS DB. In this way we can keep track of entire DB changes.
You need to be a premium member to use this feature. To access it, you'll have to upgrade your membership.
Become a sharper developer and jumpstart your career.
$0
$
. 00
monthly
For Basic members:
$20
For Premium members:
$45
For Elite members: