How do I manage stored procedures with SQL Server 2005 and Visual Source Safe 2005?

I am trying to follow the steps on the following site

http://msdn.microsoft.com/en-us/library/ms181089(VS.80).aspx

But I could not find the Data View window and Add to Source command in SQL Managment Studio. Then I tried to modify the stored procedure and then clicked the Change Control Source button in the Version Control Panel. Apart from the SQL Server computer Visual Source Safe client connects to my Visual Source Safe backing store, I could not change the stored procedure bindings due to the following error message:

Cannot change source control bindings. Ensure that each project has a valid binding.

      

I do not know what to do next. Any idea?

0


a source to share


4 answers


Personally, I don't use Source Safe directly from SQL Server to track database artifacts, I create a database project and link it to Source Control.



By doing this, you maintain Source Safe's integration with Visual Studio and SQL Server.

+2


a source


Write the stored procedures in script files and copy them. When you make changes, edit this file and commit it as normal source code. Scripting your stored procedures will also save you time later if you want to script out of your database.



+2


a source


Have you checked the source control settings in SQL Management Studio? Tools> Options, then Source Control. Make sure SourceSafe is installed as the current version control plug-in. I think for your scripts, you can create a script project (File> New> Project> SQL Server Scripts) and then start adding scripts. If you right click on the project script, you will see "Add solution to source control".

+1


a source


Check out this site: VBScript with SQLDMO is basically what we do internally at home, we wrote a vbscript file that uses SQLDMO to dump the contents of all SQL objects into a directory, then we use SourceSafe object through vbscript to control version control. Unfortunately, I cannot post the code as my boss also visits this site frequently;)

We recently switched from VSS to TFS and wrote a process to manage this in .NET, handle a lot of clean.

0


a source







All Articles