588 results found
-
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 me to specify what tables to sync instead of a Database
In our environment multiple projects make ddl changes to same database. But they dont make changes to a same table/procedure. It would be nice to have advanced settings which let one specify what objects go to what folder instead of an entire database.
5 votesIn v2.2, which is expected to be released in the next few weeks, we’ve implemented Object Filtering, which allows you to specify which objects to inlcude/exclude for source control. Therefore, you could link a database and set up a filter so that only the tables/procedures your interested in for your project would be source controlled. Would this help?
You can get the v2.2 Release Candidate at http://www.red-gate.com/messageboard/viewtopic.php?t=13668 to try this out. -
match SMO output
I've written my own tool to do this --- a heavy edit of http://www.codeplex.com/scriptio actually --- and this new product differs in at least three respects: the white space (indenting tabs, blank lines), the directory structure (example: "Functions" and "Stored Procedures" should be under "Programmability"), and extra command (example: CREATE USER has CREATE LOGIN and GRANT CONNECT around it). Why not match the SMO output exactly?
5 votes -
Change btn txt on the 'Get Latest' tab.
Button says Get Latest. Incorrcet Subversion term. SVN Update or something similar will prevent the confusion.
5 votes -
Only work on selected objects
Refresh/Commit always is performed on all databse objects. Even if I just change 1 object, I have to wait until all is refresehd, unselect all changes that I don't want (from other objects), commit and then wait again until everything is refreshed.
By default the refresh/update/commit should only be used for the select object(s) in the object explorer. You can offer configuration or buttons to "refresh all" or a checkbox "perform for all objects".
The automatic refresh eats unnecessary time during development.
5 votes -
Source control options.
There need to be some options for how the code is written to source control. We have strict requirements and all our code must go in with a required header to it. It would be perfect if we could put this header in SQL Source so all code coming in would always have it. That way when changes occurred to that header we could more easily make a change. The other more important issue however is user rights assignment. Currently each object stores what user has rights to that object in the database you keep synced with source control. That…
5 votes -
Add "Save as..." option to history window?
We have a 3rd party developer who sometimes tweaks things on our databases, i have to report and document these changes to management, currently, i have to either rely on screenshots, or copy and paste the before & after code and apply my own colouring etc. Something similar to VSS's change report would be ideal: example: http://www.heavencore.co.uk/filehub/Documents/ssreport.txt
5 votes -
Invalid object name
Hi,
When doing "Get Latest" on objects which hold non-existing dependencies you get the following error and action fails until you manually identify and deselect the objects or modify the SQL script :
Msg 208, Level 16, State 1, Procedure myl33tprogrammer_proc, Line 4
Invalid object name 'dbo.table1'.Proposing the user to ignore dependencies error messages or to deselect automatically problematic items could improve the "Get Latest" feature and avoid time loss in manual actions.
5 votes -
source control version 2.2.1.16 takes forever to get latest , SQL 2008 R2, TFS
source control version 2.2.1.16 takes forever to get latest , SQL 2008 R2, TFS
5 votes -
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 -
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 -
StarTeam
Include StarTeam as a source control option
5 votes -
Accomodate for people with colour blindness
One of my colleagues has colour blindness.
The distinction between a non-reviewed database (the grey circle) and a database with outstanding changes (blue / white icon) is difficult to see because of the fact that the icons are so small (the less pixels to compare, the harder it is by all accounts) and often can be far away (i.e. if there are other non-source controlled database between them on the database tree in SSMS).
It would be helpful to make a clear distinction between the icons - either make the grey icon a flat colour (i.e. remove the highlight within…
5 votes -
Why do you have to be in sysadmin-role to see who checked in changes?
Ít would be nice, if you dont have to be in sysadmin-role to see wich user has made changes. thx.
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 -
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 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 -
Add Support for SVN Keywords $Rev: $ and $LastChangedBy: $
Add the ability for SQL Source Control to update or make use of the $Rev: $ and $LastChangedBy: $ SVN Keywords
5 votes -
Allow user to disable dependant object refreshing
When getting latest SQL Source control always tries to refresh dependent objects. We have a scenario where we know we have broken objects (large database cleanup) and get latest fails because it tries to refresh those objects.
Add an option where users can skip that step. It currently generates code like below:
IF @@TRANCOUNT=0 BEGIN INSERT INTO #tmpErrors (Error) SELECT 1 BEGIN TRANSACTION END
GO
PRINT N'Refreshing [dbo].[vSomeView]'
GO
EXEC sprefreshview N'[dbo].[v_SomeView]'
GO5 votes
- Don't see your idea?