March 17, 2007 at 3:33 am
Hi,
I am currently trying to set up Visual Source Safe 2005 to interact with SQL Server 2005. I think I am over the worst of it now but I have a question regarding connections.
Each database has been created as solution with stored procs, views etc being created as projects beneath. This setup works fine except for connections. Everytime one of my team open a project query in our development database they have to associate their windows connection with the script to open it. This checks out the .ssmssqlproj each time as it has to update the associated connection information.
I want to get round this problem because it means that when a query is opened the connection has to be changed and the .ssmssqlproj checked out even though you may just want to run the script without making any changes (read-only). Is there away round this?
Thanks
Jon
March 20, 2007 at 1:09 am
Use Copy-Modify-Merge Model in Visual SourceSafe or remove .ssmssqlproj file form the Visual SourceSafe
This is not an exact solution for the above issue.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply