June 13, 2003 at 5:04 am
VS.NET is a great programming environment for Stored Procs and UDF's, however only procs are integrated with Visual SourceSafe. What are other people doing for Source Control on UDF's (i.e. how do I prevent someone editing a UDF I have checked out)?
June 13, 2003 at 11:02 am
I don't know if this is an answer to your question, but VSS does not have to be integrated with your IDE for you to use it. In other words if you access VSS directly you can store what you like in there and you will have source-control.
We use it extensively for all sorts of scripts including SQLAgent job-scripts by this method, as well as storing our VB and VB.NET project sources through the direct integration
I have found it is possible to please all of the people all of the time if you do exactly what they want. Harold Macmillan 1961
I have found it is possible to please all of the people all of the time if you do exactly what they want. Harold Macmillan 1961
June 15, 2003 at 11:38 pm
Have you taken a look at mssqlXpress it provide Visual SourceSafe intergration for all SQL objects. http://www.mssqlXpress.com
June 16, 2003 at 1:06 am
>>What are other people doing for Source
>>Control on UDF's (i.e. how do I prevent
>>someone editing a UDF I have checked out)?
Have a look at SQL Source Control 2003 - looks very promising indeed:
http://www.skilledsoftware.com/
Integrates tightly with SourceSafe, allowing you to put all your DB-related SQL code (not just UDF's, also table creates etc.) under SourceSafe's control.
Marc
June 16, 2003 at 4:04 am
I use VS.NET for all my database objects, not only SP's. If you select all your tables, views, ect in your database, right-click and choose "Generate Script..", you can make scripts for all your objects. Just choose a map that is part of your database project, and VS.NET takes care of the source control part of it.
I have used the IDE extensively and i found it a very good way of controlling my database changes.
June 16, 2003 at 9:22 am
Thanks for all the responses.
I realize that you can generate 'Create function' scripts and use VSS outside of VS.NET to version control the script files. However, this is 'Version-control', not 'Source Control'. The distinction is that you are not prevented from altering the 'checked-in' SQL object from the VS.NET environment, the way that you are with stored-procedures.
I will look at the other two products that have been suggested. I was hoping to be able to stay with the VS.NET environment for Sql development, instead of having to move my entire staff to a new IDE for lack of this one feature...
June 16, 2003 at 12:08 pm
You Can use the IDE for all the other database objects as well. Beleive me, it is worth a try. I have worked with it for a while and it provides you with enough tools to keep your database versions in control.
If you want to alter an object, just alter the script that is under source control, and not alter the database directly. Just use the database for testing the changes and put them under source control if you are sure the changes are right.
June 6, 2007 at 6:16 am
Is anyone out there aware of any news on VSS/SQL integration support for UDFs?
(My company doesn't use SQL UDFs because there is no *source control* integration within the VS.NET Server Explorer IDE; as there is with stored procedures. Consequently there isn't any way to prevent developers from overwriting each others code when working within the VS.Net environment.)
Viewing 8 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply