53 results found
-
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 -
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
-
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 -
Partitiong Functions
Without any changes on the database, SQL Source Control creates a tracked changed alternating between these two partitioning functions:
CREATE PARTITION FUNCTION [TranDate] ([datetime2] (0))
AS RANGE LEFT
FOR VALUES (N'2007-01-01 00:00:00', N'2008-01-01 00:00:00', N'2009-01-01 00:00:00', N'2010-01-01 00:00:00', N'2011-01-01 00:00:00', N'2012-01-01 00:00:00', N'2013-01-01 00:00:00', N'2014-01-01 00:00:00', N'2015-01-01 00:00:00')and
CREATE PARTITION FUNCTION [TranDate] ([datetime2])
AS RANGE LEFT
FOR VALUES (N'2007-01-01 00:00:00', N'2008-01-01 00:00:00', N'2009-01-01 00:00:00', N'2010-01-01 00:00:00', N'2011-01-01 00:00:00', N'2012-01-01 00:00:00', N'2013-01-01 00:00:00', N'2014-01-01 00:00:00', N'2015-01-01 00:00:00')Could something be done about it?
5 votes -
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 -
spinning wheel icon
After creating the database, I added to the shared database model and commited the objects to the repository, but the spinning wheel is not gone and it looks like it is busy or just unable to reset the icon. Even after I disconnect from the database server in my SSMS, my cursor still has the spinning wheel on it. Looks like a bug and it is really annoying and confuses the hell out of users about the status of Source Control process.
5 votes -
Do not allow to commit changes to an object that is locked
I don't see why is good this product if it's posible do commit to an object that is locked. If the object is locked this means that the user is editing it Then why allow to commit to this object
5 votes -
5 votes
-
4 votes
-
Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users
Feature which should enforce user to lock the object before editing when administrator enables the restrictive policy for the users
If it is there it will be very much helpful for most of the development projects not testing and production.
4 votes -
Login information for SQL Source Control
Where login information is stored for SQl Source Control 3? If A user is using B users SVN credentials and later on A user get its own SVN credentials. How user A can force SVN to ask his own credentials?
4 votes -
When a user closes a session/SSMS it would be useful to have the user to prompted about any pending check-ins (shared db).
We use a shared environment, and if someone forgets to check something in, then the changes made appear as if from the next user to edit the item.
4 votes -
Drop statement in script
Would be nice to have the option to include the drop statement inside of each object script. The option would be global over all scripts.
EX: IF (OBJECT_ID('MyTable') IS NOT NULL) DROP TABLE MyTable4 votes -
4 votes
-
On shared mode, Source control sync delayed issue
Shared mode is perfect for small team DEV environment, but status update delayed to sync is annoying....is there a way to config the sync frequency?
3 votes -
BUG: Sql Source control doesn't maintain WITH (IGNORE_DUP_KEY=ON) on table type
I have a table type with "(IGNOREDUPKEY=ON)" on it. Sql Source control doesn't preserve this and doesn't see this in the SqlServer database schema on the table type
3 votes -
Changing a data type used in a SP creates problems
When changing a data type used in a SP (e.g. add a new column to it and commit it). getting latest fails on other linked DBs. You have to drop the SP on the target DB.
The weird thing is that sometimes it works, but most of the times it doesn't. Not sure why the behavior is not the same all of the times...3 votes -
Commit dependencies dialogue blue dot.
Commit dependencies dialogue shows blue dot on objects even when those objects have no changes to commit. This seems incorrect.
3 votes -
I am allowed to commit previous changes that upon refresh would show newer changes. Can there be a check for this on commit?
I want a check on commit for all the items I intend to check in to make sure that there is not a newer version available. In the case where there is, I want to be presented with a list of those changes for review before anything is committed.
2 votes -
SSH Passphrase
I am not able to push changes to my repo using SSH because I am unable to enter my passphrase. I have to push/pull using Git Bash.
2 votes
- Don't see your idea?