Skip to content
← SQL Source Control

How can we improve SQL Source Control?

SQL Source Control: History/Log

Categories

JUMP TO ANOTHER FORUM

(thinking…)

I am looking for the report to track who has made the changes and not checked in.

Hi,

I need to know who all has not checked in/committed the code the code.

As we have so many databases to work on and its very hard to see one by one

Thanks,
Vijay

5 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…)
VIJAY AELLA 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
  • AdminDavid Atkinson (Product Manager, Redgate) commented  ·   ·  Report

    You could consider running the SQL Compare command line to compare a dev DB with the contents of your version controlled repository. This will tell you what hasn't been checked in, but won't tell you which developer is responsible (unless you each have your own dev instances).

  • GARY SINGH commented  ·   ·  Report

    We have 70+ databases and 50 developers and this report or GUI interface will help to see all the objects checked out across all databases from all the developers.

    If this feature is difficult, a T-SQL script to extract this data would be really helpful.

    Thanks