588 results found
-
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 -
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 -
Changes to data in Static Data Linked Tables should be included in the Migration Script, just as changes to the schema are.
If a table is linked as static data, any changes to the data should automatically be included in the migration script, just as changes to the schema are. Having to write a manual script or use the separate compare tool is extra work, and small changes are easy to miss.
43 votes -
User permissions should be separated from the stored procedures/functions/table definitions
In our set-up there are two databases, one that's used as a template and an actual working database for the application we're developing. The development takes place in the template database and then the changes are moved over to the working database (we have a staging database in which we test the changes with real data).
We would like to link the staging database to source control so that updates to it can be applied easier.
The problem is that we're using user-based authentication to allow only specific users access to specific stored procedures and SQL Source Control treats user…
38 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 -
Option to switch order in diff panel (script for database version vs. source control version)
In the diff panel, I would prefer to see the current version in source control on the left, and the database version on the right, as that's the same existing -> new order as all my other source control tools use. How about an option to do that (that would be remembered on restart of course)
9 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 -
When committing, show when multiple people have edited an object
When comitting:
Andy makes an edit and "Changed By" shows "Andy" (but does not yet commit).
James then makes an edit and "Changed By" is now "James", but does not mention "Andy"It would be useful if it could show "Andy, James", to highlight a potential conflict.
18 votes -
Show whitespaces as differences in the comparison report
I enable in the comparison option to show me any whitespace differences between my source and target.
This changes will be shown by SSC from now as a difference, but not visualized in the comparison window. At least it's showing me that there is difference.
It would be really nice if the differences could be visualized like SQL Compare is doing it.
Regards
Robert1 vote -
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 -
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 -
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 -
Improved object merge support - Provide ability to merge a conflicted object, instead of just Keep Mine or Take Theirs
I have seen no way on how to actually do a merge with SVN and mark as merged etc
We really need a more inutuitive way to merge the changes to SVN and vice versa. At the moment I am getting conflicts that I can't put into SVN because there is no way to say it has been merged, or even how to merge the changes.131 votes -
on the conflict resolution screen, easier way to page down through lots of conflicts and 'take mine'
would be really nice on the conflict screen if you didn't have to click up on the row then move mouse down to option button way at bottom, 185 TIMES! If you could just select a range and say 'take mine' or page down with arrow key and hit an F key F1 mine, F2 Theirs...
7 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 -
Agent jobs
Would be great if SQL Server Agent jobs could be incorporated into SVN
480 votesThank you everyone for your comments and votes on this over the years. While I don’t have a 100% full resolution for this suggestion, I can sum up our current recommendations here. Continued feedback is very welcome.
Our current recommendation is to use the post-deployment script feature of SQL Source Control (released in V6.3) to manage SQL Server Agent jobs.
An example script for this is here: https://documentation.red-gate.com/soc/common-tasks/working-with-pre-post-deployment-scripts/create-sql-server-agent-job
As some commenters in this thread have alluded to, it is possible (and sometimes very common) for SQL Agent jobs to have steps that touch multiple databases on a single SQL Server Instance. For this reason, some customers prefer to create a separate database for instance-level management and objects (sometimes named DBA or similar) and choose to manage things like linked servers and SQL Agent jobs with the post-script associated with that database.
This separate-database architecture also makes sense if the jobs…
-
Track server-level security (logins, etc.)
Would like to be able to track the server-level security in source control. Logins, Server Roles, etc.
10 votes -
Provide ability to delete/drop objects from TFS / DB
If from Get Latest / Commit changes it is determined that an object shouldn't exist, currently there is no way to drop the object from the db, or delete it from TFS, via the SQL Source Control UI.
3 votesI don’t understand… If someone else committed a drop of an object, then once you click the “Get Latest” button on the “Get Latest” tab, then it will drop if from the db.
-
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 -
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
- Don't see your idea?