588 results found
-
Database Diagrams
Support to check-in database diagrams
156 votes -
Work with a Visual Studio Database Project
Can this work if I already have a VS Database project setup? Meaning can this work and interact with a VS Database project so that I can continue working on the actual db in SSMS, but the files get saved to the VS Db Project?
215 votes -
Possible bug: lost check ins?
Okay, this can be VERY serious! I want to discuss this here in case someone else has similar effects: for several months now (i.e. also in earlier SourceControl versions), we had lost check ins! It occurs very seldom and so far, people said "you just forgot to check it in". But now, several people had the same effect that a successfully checked in stored procedure was just lost! The history does not show the change that the user successfully check in! As this occured about 3-5 times in the last months just for my user account, two other people are…
2 votes -
Implement Source Control for PostgreSql
Can you implement Source Control for PostgreSql?
26 votes -
Provide a way to enter bugs
Your feedback system should allow for a way for a user to input bugs that they find.
For example, allowing unselect all for existing changes.
I've never been a fan of SQL source control, and this product has made me dislike it even more.
1 vote -
.AssemblyLoadHackery
.AssemblyLoadHackery
1:We attempted to load RedGate.Update.Client, Version=2.3.0.237, Culture=neutral, PublicKeyToken=7f465a1c156d4d57 from C:\Program Files (x86)\Red Gate\SQL Source Control 3\RedGate.Update.Client.dll, but got RedGate.Update.Client, Version=2.3.1.308, Culture=neutral, PublicKeyToken=7f465a1c156d4d57
1 vote -
The undo feature automatically disables your database triggers. I don't want my database triggers disabled.
We use DB triggers to track schema changes. If we use the Undo feature, it disables the triggers and we no longer are able to record the history apart from our source control system. Source Control is great, but we need to know exactly who made changes and when.
2 votes -
Allow users to copy the complete error message
When an error occurs, I would like to be able to copy the error message so I can research it. I am unable to select the "complete error message" text so I cannot copy it. It's a simple thing, but it really would be nice to have.
5 votes -
Need ability to suppress conflicts about constraint name changes.
We frequently execute DB scripts on dev machines and servers, and when default constraints are created in SQL they are given a randomized name. Since we have SQL Source Control installed in the same environments, we always get conflicts about the constraints being named differently in the source control vs. the current machine. The ability to turn of conflict (or even change) notification about some things like constraint names is needed to avoid having to deal with each case individually.
9 votesSQL Source Control’s Get Latest should be used in a dedicated model to update your different dev machines. This would keep the constraint names consistent in your dev environment.
You can use SQL Compare to deploy changes to other environments. SQL Compare has an option to ignore constraint and index names so that these differences won’t appear.
-
Allow an option for indices to be created / rebuilt using the "with(ONLINE = ON)" option
Allow an option for indices to be created / rebuilt using the "with(ONLINE = ON)" option
6 votes -
Allow users to change the Transaction Isolation Level. Serializable causes problems with linked servers.
Ever since updating to 3.6.0.3, the default Transaction Isolation Level in deployment scripts is Serializable. If a stored procedure has a reference to a linked database it will fail. I have to manually edit every script now and change it to Read Committed...
4 votes -
Support change data capture (CDC)
When enabling change data capture on a database, source control does not pick up the system tables created, nor the changes to the database configuration. It is only able to gather the schema, role and function changes
22 votes -
1 vote
-
Display date of changes
We are using this in an active DW environment. The date of the change would be a helpful SSMS column. We like to see what changed, even in non-checked in work.
1 vote -
Suppress credentials prompt when SSMS starts
Sometimes when I launch SSMS I see the "Source Control Credentials Required" dialog.
"""
Your source control system requires credentials.Enter the user name and password for the repository:
"""It's prompting me to update the expired credentials for one of my old development projects.
I don't want to update the credentials right now, but SQL Source Control is very persistent about it.
When I click Cancel, the dialog immediately reappears!
After clicking cancel about 10 times in a row, it finally stops asking.
Can you suppress the dialog on startup?
It would be better to ask only when it…
3 votes -
On the "Get Latest" page, provide a way to globally un-check all objects
Can you please provide a way to "Uncheck" the entire list of objects on the "Get Latest" tab. I have 100+ objects ( Team of 6 Devs ) to get latest and 3 or 4 objects have issues, so I have to manually uncheck each of the 100 checkboxes and then check just the ones I think are ok to check in
1 vote -
Add filter option for filegroups
Add an option in the SSC filter to ignore differences in filegroup location as there might be multiple instances of a controlled database that have different filegroup configurations
6 votes -
Allow an option to exclude members of database roles from SSC.
We like to control access to objects using database roles. However, the members of the roles are different in different environments (dev, test and live). I want to include the roles (and their permissions) in SSC, but don't want SSC to worry about the members of the roles - this can be handled manually.
19 votes -
Add Filter to Migration Scripts
Add Filter to Migration Scripts
When you go to create the migration script, you get to choose which commits are part of that script. It would be great to sort the migration script by the product descriptions or tags. When we have multiple commits to a database, and we might commit #project1 and #project 2 back and forth for a month, and instead of having to ctrl click through every other one, it would be great if we could group them together (or filter) and then generate the migration script easier.
5 votes -
Allow Filter by object Type
It would be really great if there was an option to filter exclusions from source control by object type in addition to the Schema and Name as it is presently.
3 votes
- Don't see your idea?