December 14, 2005 at 5:17 am
I understand that SS2005 is fully integrated with Source Control. In order to do this does everyone have to work off the same database? Or will it be possible for each developer to have a local database that they can check out their stored procedures to?
December 15, 2005 at 3:36 am
Source control, I believe, is achieved by integrating BIDS and VSS. The question about operability on different databases will be down to the coding of your packages to run on a given rather than specified database.
December 16, 2005 at 1:00 am
I am not sure exactly what you mean by "SS2005 fully integrated with Source Control". I would definitely not say that is true. SQL Server Management Studio (and BIDS) is integrated with source control so that you can have your script files versioned. That is about it. It does nothing special to make a database synchronize with source control or anything.
December 16, 2005 at 4:55 am
Everwhere I've read about SQL Server and source control say it is "fully integrated" but thats all they say.
I want to know if it works like VSS does with my C# code. I check a file off the server and it puts writable version of the file locally on my local machine.
If I have my stored procedures in source control on the server, and I check it out, will it put the latest version of that stored procedure in my local database?
December 16, 2005 at 5:09 am
Like I said, the only thing that is under source control are files. You cannot pull a stored procedure from source control. If you have a script that creates that stored procedure you can checkout that script file and edit it, create the stored procedure etc.
December 16, 2005 at 5:14 am
Is there any way to keep protect stored procedures in a multi-user environment?
December 16, 2005 at 8:28 am
There is an old way in Visual Studio to create a database project under other projects. Then it integrates with VSS. That will allow you to have a central VSS database. Check out and all that stuff.
I was also hoping SSMS was going to have that feature integrated and have not found an answer yet.
December 18, 2005 at 6:00 pm
There is a great new feature called DDL triggers. You can easily create a DDL trigger that disallows any changes to schema, for instance procs.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply