Is there a plug-in for SQL 2005 management studio?

[Bo Guan]

Need to add the sql sp and scripts to scc. Is there a Valut plug-in for SQL 2005 management studio?

[lbauer]

Vault doesn't officially support integration with SQL Server 2005 Management Studio, but some users have gotten it to work in the same way Visual Studio does.

See this links for more info:
http://support.sourcegear.com/viewtopic.php?t=5820
http://support.sourcegear.com/viewtopic.php?t=5943

[Jamie Clayton]

I think that it is essential for Vault to consider adding support SQL Server Management Studio (SSMS) in it's product range. For the same reason that we have application source control, Database Source control is a must!

We setup SSMS solutions with the following 3 projects Development, Testing and Production with SQL Scripts for application moving *.sql script files through each of these projects as our applications (in Vault) move through the same life cycle.

Eg. MyDBApplication.ssmssln contains the following text

Code: Select all

Global
	GlobalSection(SourceCodeControl) = preSolution
		SccNumberOfProjects = 3
		SccProjectName0 = $/SQLServer2005/MyDBApplication
		SccLocalPath0 = .
		SccProvider0 = MSSCCI:SourceGear\u0020Vault\u0020VS2003\u0020Compatible\u0020Client
		CanCheckoutShared = false
...
EndGlobal

This allows me to "use" vault as a source control.

The projects files bellow the solution, E.g. Development.ssmssqlproj that file had text like the following for VSS, but I remove this manually to get the solution working with Vault.

Here is the VSS version of a project's files source control:

Code: Select all

<?xml version="1.0" encoding="utf-8"?>
<SqlWorkbenchSqlProject Name="Development" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
..Removed...
SccProjectName>"$/SQLServer2005/MyDBApplication", OELAAAAA</SccProjectName>
   <SccAuxPath />
   <SccLocalPath>..</SccLocalPath>
   <SccProvider>MSSCCI:Microsoft Visual SourceSafe</SccProvider>
</SqlWorkbenchSqlProject>

Note: After doing this to your solutions and projects get a constant "request" to match the projects source control with the solution, which is annoying, to say the least.

With this combination I can get the developers of various application to add there "Database" changes to scripts Eg. \Development\MyDBAv1.2.3.4.sql which then migrates (moves) to \Testing\MyDBAppAv1.2.3.4.sql and then eventually to the production project.

This allows us to monitor what applications and changes are in the 3 phases of our application release process. Our company separates Database changes from our applications (Visual Studio) to restrict the volume of developers who make database changes. It's possible for more than one application to connect to a database. The Databases with our software solutions are often used by more than one application.

Now I know we could change our application Source control (VS) to include some of the SSMS *.sql scripts, but Microsoft seem to be making an effort to use "similar" IDE's for users, so I would hope that Sourcegear might follow suit and add a "better" provider for SSMS.

FYI, we also use other database version control software from Red-Gate to manage version control between releases of applications (matching database changes), so all I'm really interested in is a better implementation of Source Control with SSMS.

I would be interested in other peoples experience or expectations of Vault and SSMS. The Microsoft SSMS developers have been particularly interested in how we have chosen to use SSMS and I would expect that improvements to SQL 2008 will reflect the higher expectations of the IDE provided by Microsoft.

I hope this will start a healthy discussion on the topic.

[lbauer]

Thanks for your comments and the feature request. We have had other requests for SQL Server integration, particularly with SQL Server Management Studio. I'll add your suggestions to our feature tracking database. This is something we'd like to add in the future, but we don't have a target date for implementation as yet.

[jclausius]

James:

Modifying the projects by hand won't necessarily work as the support files that go along with project binding will be missing.

We haven't added SSMS to our supported IDE list due to lack of a thorough testing. However, in my initial attempts everything does seem to work OK.

Try this:

1) Set Vault's MSSCCI client as the Source Code Provider within SSMS.

2) Add your NON-BOUND database project to Vault's repository (File -> Source Control -> Add To Source Control ). Follow the dialogs to add all related files to Vault's repository.

3) For the FIRST GET, other users can do step 1, and then go to File -> Source Control -> Get Project From Source Control). Choose the project's solution directory, and set a working folder.

4) For SUBSEQUENT opens of the project by the person who added the project as well as other users, just open the database project from disk. File -> Open -> Projects -> Choose the DB project.

HTH

[Jamie Clayton]

Thanks for that information. I've just imported all my VSS projects, including the SSMS solutions/projects and was trying to swap source controls. I'll admit to being a little frustrated trying to get it working. I spent a couple of hours working on this.

These were my internal instructions (which I'm going change based on your advice).

1. Opened the Solution and select “Unbind” from the Source Control Window.
2. Manually checked out solution and project files as required.
3. Manually modified (notepad) the *.ssmssln file with the following
Global
GlobalSection(SourceCodeControl) = preSolution
SccNumberOfProjects = 3
SccProjectName0 = $/SQLServer2005/MyDBApplication
SccLocalPath0 = .
SccProvider0 = MSSCCI:SourceGear\u0020Vault\u0020VS2003\u0020Compatible\u0020Client
CanCheckoutShared = false
...
EndGlobal
4. Manually modified (notepad) the *. Ssmssqlproj files by removing the following elements
<SccProjectName>"$/SQLServer2005/MyDBApplication", OELAAAAA</SccProjectName>
<SccAuxPath />
<SccLocalPath>..</SccLocalPath>
<SccProvider>MSSCCI:Microsoft Visual SourceSafe</SccProvider>
5. Checked in the files to source control and cross checked the working directories.
6. Shut down and re-opened the solution.
7. CATCH: you get a very silly warning message when you open the solution
“The project file xxx\xxx.ssmssqlproj is not bound to source control, but the solution contains source control binding information for it.
Do you want to open the project using source control binding information from the solution or open it as unbound and fix the solution file?”
8. In this dialog box you need to check the option “Apply this option to all projects being opened” -> Click on the “Use Solution Binding” button.
The source control menu options seem a little “confusing” in SSMS as there is an overlap of menus with VSS.

[jclausius]

I think what may be happening in the case of manually modifying the files is that the support files which control repositories , repository paths, etc. is not being written to disk leaving you in a half-baked state.

The Open From Source Control and Add To Source Control worked fine in my limited testing.