588 results found
-
Directory and File Locations
Allow the ability to control the location of ALL files/data (permanent and temporary and logging, etc) associated with SSC. This should be asked during setup, but should also be user configurable after install.
1 vote -
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace is simply not accep
Increase performance of SQL Source Control when using Static Data. Even with small amount of static data the performace of the tool is not acceptable.
24 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 -
Disregard pending changes WITHOUT revert
It can and does happen.. you end up with objects that you know are in production but for whatever reason never got committed and put into a migration script. Or, you just aren't interested in ever putting a certain change live.. maybe they are dev only. Maybe they are irrelevant objects like users. Maybe a naughty dev put stuff live without going through the proper process.
In all the above cases I want to be able to remove the object from my "pending" list without reverting. I want to ignore them completely.
I am aware of the ability to filter…
1 vote -
Customize headers, footers and batch footers in migration script
I'm hard pressed to think of any corporation that would take a migration script and run "as is". You will at the minimum have some standard code or comment block to put at the top and bottom of a script.
For example, in our particular place, we check the DB version before running a script (header), and stamp a version on success / error handle (footer).
We also have special statement which we need to put after each batch (where the migration currently places a "GO").
Needless to say, having to manually do this is time consuming. So my suggestion…
5 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 -
Automatic source control migration scripts facilitation/generation/recording.
When using development tools to modify a schema, you can end up having applied a number of changes which cannot be applied without data loss using schema differencing and which need to be included in a migration script.
It would be helpful if there was some form of SQL trace which could monitor schema changes actually applied, and be used to generate a composite migration script.
If I use Enterprise manager, or Red Gate to refactor the schema, it is up to me to remember to save the generated SQL and any other SQL I might write along the way…
1 vote -
Add ability to execute all tSQLt tests before commit, if one or more fail abort the commit
Add ability to execute all tSQLt tests when committing the database changes, if one or more fail abort the commit and show error messages.
2 votes -
Ability to commit all databases on a given SQL Instance at one time. No need for per-database commits.
Too much effort involved to commit multiple databases. Need the ability to right-click at the instance-level, and initiate a check-in for all databases with affinity to a source-control provider.
8 votes -
Override the comments italicized text when entering a comment
When committing changes, the text area shows a default message that states: "Type a comment describing your changes..."
It would be ideal if you could override this statement with one of your own in some sort of a configuration file:
Ex: "Comments are required, please reference ticket number before checking in your code..."
Speaking of a configuration file, why isn't there one???
3 votes -
Support SQL Azure for large database development
I know you already declined another request to support SQL Azure on the grounds that you do not recommend using SQL Source Control on a production database, but please reconsider supporting SQL Azure for development.
22 votes -
object revisions
Perhaps this already exists, but I couldn't easily find it by searching. We are using SVN as a backend. When checking in files, the "revision" number seems to be incremental based upon a global revision number, and NOT the actual revision number of the object being checked in.
If I'm creating a brand-new procedure and I check it in, the revision number should be 1??? Not 152 or some other number.
This way, after many changes, of when I want to go back to a prior version, you can easily find it!
Can this please be added?
8 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 -
Simplify datalink source code repository migration
We recently migrated our svn repo to HTTPS and part of that process was for our devs to update their SQL Source Control datalinks.
We ran into 4 issues:
1) When opening SSMS for the first time, we were inundated by SQL Source Control to update our credentials.
2) After hitting cancel 10 times, we were able to get to the Setup tab. Where we thought we could just edit the existing link, but instead we had to Unlink the database first.
3) After unlinking, all the options on the Setup tab disappeared requiring a restart of SSMS. I can…1 vote -
prevent timeout on commit changes tab for larger db in shared database model
prevent timeout on commit changes tab for larger db in shared database model
6 votesThe timeout occurs when SQL Source Control runs a SQL query to find out which user made the changes that need to be committed, and the server takes too long to respond.
SQL Source Control 3.6.0 improves this situation, so that if a timeout occurs you can still go ahead with the commit. This version is currently available on Frequent Updates. To learn how to turn on frequent updates, see: http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates
-
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 -
Database name flickering in Object Explorer
Version 3.5.3.29
SSMS 2008 Express, connected to local 2005 Express instance, running on Windows 7 as a guest within VMWare Workstation.As standard I have all my databases offline, and bring them online individual as and when required.
The database name in the Object Explorer shows the "spinning" white and blue dot - but is constantly flickering/flashing. It will do this until the "Commit changes" or "Get latest" tab has been viewed... even if the Source Control screen is not even open (let alone having focus).
The only way to stop it is to open SQL Source Control and refresh…
3 votes -
Auto create migration scripts prior to a comit
Auto create migration scripts prior to a comit.
I would like to sugest that SQL Source control should have the ability to auto create migration scripts prior to a comit. This should be a configuarble option that can be enforced at the database level. By offering this we as developers could see and archive the expected migration path from x to y to z. Obviously any auto created migration script should still be editable as it is now.Thanks
7 votes -
Selective XML Indexes
Correctly support SQL Server 2012 Selective XML Indexes (SXI). Currently any SXIs are committed to source control as Primary XML indexes
2 votes -
Bug message -- An inconsistancy was detected during an internal operation in database . . .
Got an error message running a data compare:
Bug message -- An inconsistancy was detected during an internal operation in database 'DWC' (ID:5) on page (1:3531152). Please contact technical support. Reference number 7.
When I tried to find a link in the program to technical support, best match I saw took me here. Maybe you need a better link or even a "Contact Support" button which pasted the text of the message into an e-mail or something along those lines?
4 votes
- Don't see your idea?