Source Control on database objects...

Hot Topic

"passing along" files from a custom editor to standard editor
Getting Started with WPF But Can't
Execution session has expired
How to use VSTO to replace word automation letter generation
Extreme slow binary file check-in
Microsoft Office 2003 Save My Settings Wizard
ReportViewer LocalReport Export File type limitation(VS.NET 2005 beta 2)
Visual SourceSafe Internet... ?
Is there a way to specify the Z-order of an element in XAML???
Competitive upgrade license

Visual Studio

Can Sql Server Management Studio and Visual studio 2005 use the same solutions and projects in VSS?
Creating a New Mail Button in contacts page in outlook
The 'http://www.w3.org/2001/XMLSchema:schema' element is not declared
date picker not available, someone already working on it?
Is there support in WCF for Contract First?
Some errors after installing a visual studio 2005 beta2
How do I use the ScrollBar ?
"Microsoft.Sdc.Tasks" project is not getting recognized
Lan Service won't start
VSTO 2005, .NET 2.0 Custom Smart Tags

Source Control on database objects...

Hello,

I want to ask what are the possible scenarios on VSS 2005 + VS2005 Team Suite to source control dababase objects (SQL 2000) Is it still limited to stores procedures as VSS 6.0d + VS2003 do

SQL 2005 instead

Thanks.

Answer this question

Source Control on database objects...

  • Vibhu Bansal

    I see. Thanks.

    I just installed SQL Server Management Studio and seems to provide the same kind of approach based on a database type of project.

    Are there any differences between SQL Management Studio and Visual Studio for this kind of projects and control versioning features.

    Thanks!

  • Jim Gordon

    As concerned as MSFT is about whether everything they do makes you "more lor less likely to recommend Microsoft products in the future" I would have expected to see a MSFT response on this thread.  It is possible to create a database project in VS.Net and integrate a databaswe with TFS SC via this. This thread has a post from MSFT which might help.

  • LPXO

    Hello,

    VS 2005 does not have support for stored procedure version control through the server explorer. The recommended way is to use database projects to generate scripts for your SQL Server objects, then use a version control system to manage changes to the project.

    Thanks.

  • withersd

    Wow: that's pretty sad!!!

    Sorry to see Microsoft taking such a profound step *backwards*.

    Cheers,

    Mark Starr

  • newbie1928

    WOW! I can't believe that Microsoft would drop support for such a crucial piece of functionality!

    We've got a hundred or so web sites that we manage with VS 2003, using VSS Integration on SQL 2000.

    I guess this means that VS 2005 is really not an option for us. That is sad. We would really like to move to 2005, but these sites are never going to be migrated to SQL 2005 or converted to .NET 2.0. The clients would never pay for that.

    This is just one more feature of VS 2003 which is now missing in VS 2005.

    The more I learn about VS 2005, the more I realize that it's just not going to be an option for our company. Guess we're stuck with VS 2003 and .NET 1.1 for the long haul.

    Maybe all of these features will re-appear in VS 2007


  • LeandroTubia

    And what about people don’t want to switch the SQL-Server from 2000 to 2005, but want to use Visual Studio 2005 I can’t use sourcesafe through the server explorer because VS 2005 doesn’t support it and I can not use the new database projects, because the sql server 2000 is not supported Tongue Tied

  • HaggaiS

    This is bad :( Removing important features from a previous version is like a hit in the face when you discover that they are gone.

  • RWDavis

    Hi mkappl,

    You are partially correct. You will not be able to use SourceSafe from Server Explorer in VS 2005. However you will be able to use database project for SQL Server 2000.
  • Source Control on database objects...
Answer this question