SQL Stored Procedures / Source Safe / Visual Studio

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Using Visual Studio 2003 you were able to manage SQL stored procedures with
Visual Source Safe. So long as Visual Studio was used as the editor, it was
imposible to make a change to a stored procedure without first checking it
out. And once the changes were complete, the stored procedure was checked
back into Visual Source Safe. This process worked great.

But I can't see how to achieve the same level of control using Visual Studio
2005? I've looked at the VS Database Project but I can't see how to force a
check out prior to making a change to a stored procedure and I can't see how
to easily see what changes have made and make sure they're checked in.

Am I missing something?
 
Hi Richard,

Currently, in VS.NET 2005, stored procedure versioning is not supported. If
you need to put the stored procedures into VSS, you can try to create a
database project, put the stored procedures in the .sql files and check in
that database project. You can check the following thread for more
information on how to check in database project in VS2005.

http://groups.google.com/group/microsoft.public.vstudio.sourcesafe/browse_th
read/thread/fea9f07c0cdb9c4c/ba58366e5402ba6f?lnk=st&q=alin+vs+2005+stored+p
rocedure&rnum=2#ba58366e5402ba6f

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=140739&SiteID=1

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
How can 2005 be considered an improvement if it is incapable of doing the
things that were possible in 2003?

Can you demonstrate to me how scripting database objects can provide a
practical solution to this problem because I can’t!
 
Hi Richard,

This is a break change in VS2005. You can see from the google groups link
in my last post, Alin is a develper in VSS team. Many people have had the
same issue as yours. As a support engineer, I can just suggest you to put
the database project with SQL scripts to VSS, this is the only solution
currently.

1. In SQL server, script the whole database.
2. Put the scripts to the new database project you have created.

I know it's somewhat complex, but I'm trying to provide the workaround I
have.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
To script the database, right click on the database in SQL server and
select "Script database as" from the context menu.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Hi Kevin

Don't get me wrong, I'm not having a go at you personally, you’re doing a
great job. But (unless you tell me otherwise) you're also the best way we
poor users can get our point across to those powerful guys in Microsoft. So,
inevitably, you’re going to take some flack when things aren’t right.

Scripting database objects and checking the scripts in and out of source
safe is (as far as I can see) not a practical solution to the problem. This
is largely because the scripts are independent of the database – what you’re
saying is that, if we happen to remember to script the database then we can
check the scripts in and out of source safe. But there is no mechanism to
automatically generate the scripts or to force us to generate the scripts
manually. So it relies upon our developers remembering to check out the
necessary scripts. It relies upon our developers remembering which objects
thay have changed and to generate the necessary scripts. And it relies upon
our developers remembering to check them back in again. There are no controls
to stop the developer making changes without checking the scripts out first.
There is no way to for the developer to see which objects he has already
changed - i.e. to see which ones need to be re-scripted and checked back in.

Contrast this with the “old wayâ€, in VS 2003, where the developer is
prevented from making any change without first checking out an existing
stored procedure, where checked out stored procedures are clearly highlighted
in the VS IDE, where new stored procedures (that need to be added to source
safe) are clearly highlighted in the VS IDE, where differences between the
SQL database and the source safe database are identified, where multiple
developers can work on separate stored procedures from the same database,
etc., etc.

What I hope you’re going to tell me is that I’ve misunderstood the “newâ€
scripting-based solution and that (once you’ve explained it to me) I’ll see
that it’s the "wonderful new" way. I hope that’s what you’re going to tell
me, although, even if this is the case, it doesn’t hide the fact that the
underlying issue is that something that worked pretty well in VS 2003 has
simply been turned off !!!!!!

Richard Giles
 
Hi Richard,

You don't have any misunderstanding here. The former stored procedure
versioning is not available in VS2005 currently. And the database project
way is just a workaround for this. However, it not as convenient as doing
SP versioning directly.

I just double checked with the product team, and they confirmed about the
unavailability. I'm now checking with them to see if they have any future
plans to add this function to VS2005. I'll let you know as soon as they get
back to me.

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
Thanks for John's response.

Yes, Richard. I was just told by the product team that the database
versioning has been integrated into the Visual Studio Team System, in which
we provide full db schema version control capability which is not currently
enabled at the VS Pro level.

http://msdn.microsoft.com/vstudio/teamsystem/dbpro/

Kevin Yu
Microsoft Online Community Support

============================================================================
==========================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
============================================================================
==========================

(This posting is provided "AS IS", with no warranties, and confers no
rights.)
 
....agree, and I've just placed the expense justification with our finance
dept for the upgrade from Team Edition for Developers to Team Suite, but I
still think MS should have kept the old VS2003 functionality in VS2005!
 
Back
Top