Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control

Categories

JUMP TO ANOTHER FORUM

(thinking…)

Work with multiple databases at a time

Why not offer a "SQL Source Control" entry in the right-click menu for the instance itself, so that I can look through/update/commit changes to/from several databases at once? Why do I have to specify a separate link for each database I'm interested in? Starting at the instance level would allow me to not only find all changes, it would also permit tracking objects within the instance but outside any database, such as "Security/Logins", "Security/Server Roles", "SQL Server Agent/Jobs", "Server Objects/Endpoints", and "Server Objects/Linked Servers".

215 votes
Vote

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
You have left! (?) (thinking…)
David P. Murphy shared this idea  ·   ·  Report…  ·  Admin →
How important is this to you?

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close

We're glad you're here

Please sign in to leave feedback
Signed in as (Sign out)
Close
Close
Submitting...
An error occurred while saving the comment
  • Olaf Krumnow commented  ·   ·  Report

    A very old idea, but now I'm in the situation to need it, too.

  • Anna commented  ·   ·  Report

    This would be fantastic! We often have to multiscript a change to 28 interrelated databases across 19 instances. It has taken me hours to check in these changes!

    Between waiting for the commit tabs to refresh over 2,000+ database objects, scrolling through said objects and check-marking each one independently...it makes me want to jump out the window.

    Some kind of batch check-in ability is crucial!

  • Manikantan commented  ·   ·  Report

    Having the ability to work at instance level would be awesome. If we can save Server level
    a) permissions,
    b) Configuration,
    c) roles,
    d) logins
    it will help a lot!!

  • DataDog commented  ·   ·  Report

    I need to commit changes across ~8 databases in 1 SVN transaction

  • Paul commented  ·   ·  Report

    Ability to check in or get latest at the instance level, covering ALL databases would be a real time saver.

  • Tom Bruinsma commented  ·   ·  Report

    Our application contains a number of interrelated databases. Updating requires the user to select each database and indivdually update each database, this process is extremly time consuming when the databases contain >1000 sp's. It would be helpfull if I could update all of them at one time.

  • paul price commented  ·   ·  Report

    I am always working with several versions of a database. At a minimum, I have the following:
    - Local (personal working copy on my machine)
    - Dev (shared by all developers on my project on a shared server)
    - Q/A (used by the test team on a shared server)
    - Prod (the current production version on the production servers)

    I would love to be able to have all copies of the database (Local, Dev, QA, Prod) open in SSMS and be able to determine what schema version is running on each. This could be via a right-click option or some other visible cue. I would also need to be able to report on this schema version number.

  • philcart commented  ·   ·  Report

    This could easily be extended to include server configuration items, ANSI settings, etc...