179 results found
-
Treat renames as renames instead of a drop and an add
When renaming (tables in this instance) the commit changes dialogue says that there are drops and creations - this will possibly confuse rollbacks etc
Is it possible for the interface to "understand" renames?
55 votesSQL Source Control 3.0 is now available!
It includes a new feature called ‘Migrations’ that will help avoid data loss when renaming a table as it allows you to create, store and share SQL migration scripts for accurate deployment.
For more information about Migrations, please visit:
http://www.red-gate.com/supportcenter/Content/SQL_Source_Control/help/3.0/SSC_Working_With_Migrations -
Import sql compare project from repository by linking to repository
Hello,
we use SQL Compare and Subversion. We have already checked in a SQL Compare Script Folder. It would be great if you can use that Script Folder for link a database. In the actual Version there comes the error message that a project file for SQL Source Control is missing.
2 votesIf you were using SQL Compare to script objects to a folder and then souce controlling that, then you can link SQL Source Control to this repository and keep all your history. Information is at https://documentation.red-gate.com/display/SOC33/Using+SQL+Compare+or+SQL+Changeset+scripts+with+SQL+Source+Control. Please contact support@red-gate.com if you have any problems.
-
49 votes
The new 2.0.3 Early Access build now supports source controlling your databases with Perforce.
To get the new Early Access release please visit the following link:
https://www.surveymk.com/s/SqlSourceControl_EapSignup
Please note that we don’t support accessing the history directly from within SSMS when using Perforce.
-
Show or Filter By User who last updated on Commit List for Shared (Centralized) DB Model
One of the problems with a shared db model, where all developers work against the same database, is that everyone's changes are listed on the Commit List. It would be nice if only my changes were shown. There should be someway to filter the list to just my changes, or at least show the username in a column so that it can be sorted on.
9 votesThis feature is included in SQL Source Control v2.0, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.
If you setup your database as shared, then you will see who last updated each object on the Commit tab and Undo dialog. Only objects that you last updated will be checked by default.
NOTE: Databases linked in v1 default to dedicated databases. You will need to relink your databases to switch development models.
-
Allow commits to occur with other code changes
For continuous integration purposes, I would like to commit schema changes with changes in my project (e.g. C#) so that any related changes to classes / unit tests are commited in the same revision.
23 votesIn SQL Source Control v3.4, there is now an option to link your database to a working folder. On the commit tab, there is an option to “Save” the database changes to the working folder. This scripts the objects and static data to files. You can then use your own version control system’s tool to commit the changes alongside other changes that also exist in this area. The folder for the database needs to be separate from the other files, so it might be nice to have a top level project folder with a folder for the application and another folder for the database below. Therefore, to commit both application and database changes, you would commit from the higher project folder. You can also have more folders for documentation and other things that you want to source control.
http://www.red-gate.com/products/sql-development/sql-source-control/ -
17 votes
This feature is now available as of v1.1.0.19. Please use Help > Check for Updates on the SQL Source Control tab within SSMS to make sure you have the latest version.
Thank you!
-
Mercurial support as source control system
Currently there are only choise of SVN and TFS but I think that support of the Mercurial would be really convenient.
86 votesThe new 2.0.3 Early Access build now supports source controlling your databases with Mercurial.
To get the new Early Access release please visit the following link:
https://www.surveymk.com/s/SqlSourceControl_EapSignup
Please note that we don’t support accessing the history directly from within SSMS when using Mercurial.
-
TFS - Exclusive Checkout / SVN - Lock
It would be really nice if there was a way to checkout or lock db objects so that I know that I'm the only person working on this object and I will not experience any conflicts when I go to commit the object.
242 votesWith SQL Source Control 4.0, we have introduced our new Object Locking feature!
This feature allows users to lock the SQL object directly on their database server, meaning other users on the same server cannot make changes until you finish you work and release the lock.
-
What happens on table definition changes if I change a nullable column to NOT NULL
If i make a table column which was nullable initially to a non-nullable; and then commit this change to svn. On the other computer, when i update from svn, what happens to the data? as the records in this table may have the null values in the column i just changed.
3 votes -
Configure poll intervals
Can we have control over how often the source control / database is polled for changes? I see the changes are reflected almost immediately but reallly i dont need it to run that often - Can you let me configure how often the change polling occurs.
30 votesThe option to control poll intervals is now available from the Setup tab in the Frequent Updates build, and will be available in the next main version of the product.
If you want to get the Frequent Updates builds, more details can be found at http://www.red-gate.com/products/sql-development/sql-source-control/frequent-updates
-
Funny bug: Keep mine not working
Keep Mine has always worked fine for me until today. Now when I click on keep mine it doesn't let me mark the SP as resolvable but if I choose take theirs it does.
1 voteIf you want to “Keep Mine,” then you need to be on the Commit tab to see the checkbox at the top get selected. Nothing happens until you actually hit the Commit button.
If you want to “Take Theirs,” then you should be on the Get Latest tab. Again, the radio buttons at the bottom just acknowledge what you want to do with the object, but nothing happens until you actually click the “Get Latest” button.
So, if you’re on the Get Latest tab, you can say Keep Mine, but you won’t be able to do anything with that object until you go to the Commit tab. If you are in the same SSMS and you switch tabs, then we should remember your “Keep Mine” acknowledgement and this object should be selected on the Commit tab.
I hope this helps.
-
Checking checks/unchecks all items...how about just the one I selected?
When I first pull up the interface when I'm about to commit some changes (whether via the context menu in the Object Explorer or just clicking into the SQL SC window), you list all changes and select them all by default. That's not a big deal. The problem is, if I try to uncheck one item (not the check box at the top of the list) you'll uncheck ALL items since they're ALL highlighted.
This isn't normal UI behavior. If I'm checking one checkbox, I mean to check that one checkbox, not everything selected, even if I have them all…
5 votesHello! We fixed the issue with weird checkbox behaviour quite a long time ago. If you’re still now happy with how selection works, could you please let us know?
-
Need to output revision number upon successful commit.
You really should take a look at Tortoise. They've been doing this for a while and they really do a great job most of the time.
When I commit and it succeeds, I need the revision number that the commit generates for logging/tracking purposes. Your interface just skips over that, hiding all the information that SVN is likely returning (Tortoise will even show us what it's doing during the commit). For me, the more important thing is getting that revision. Otherwise, I have to go into a project (non-SQL) and do an update or grab the log...neither of which you…
21 votesThis feature has been added into SQL Source Control 3.5. It shows the revision number for Subversion, TFS and Vault.
Please check for updates to install. Full release notes on http://documentation.red-gate.com/display/SOC3/SQL+Source+Control+3.5+release+notes
-
Bug: renaming a SP has unlinked it from version control
I have a stored procedure sprunfacttoreport. I renamed it to sprunfacttorpt and now it is no longer in version control and changes are not propagated.
I don't mind if rename is handled by delete and add rather than svn move, but I would like every object I create to be in version control! :)
0 votesI’m glad you were able to figure it out.
Do you have your tab docked? If it’s docked, then it doesn’t auto-refresh.
-
Bug: partition function gives error when adding to SQL Source Control.
I'm getting the following error when adding the objects to subversion for the first time.
It breaks in the following partition function:CREATE PARTITION FUNCTION FDICPeoRangePartitionFn(smalldatetime)
AS
RANGE LEFT FOR VALUES('12-31-1975')This is the error:
Failed to update:
oEc.#8Jf: Errors occured whilst parsing file C:\Red Gate\SQL Source Control 0\WorkingBases\3no2fm25.di2\Storage\Partition Functions\FDICPeoRangePartitionFn.sql
'line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]'
---> #Eyg.#Lyg: Errors occured whilst parsing file C:\Red Gate\SQL Source Control 0\WorkingBases\3no2fm25.di2\Storage\Partition Functions\FDICPeoRangePartitionFn.sql
'line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]'
---> line 3:14: unexpected token: [",",<642>,line=3,col=14] [char=102]
--- End of inner exception stack trace ---
at #Eyg.#Gyg.#CGh(FileInfo file)
at…1 voteThis has been fixed in the latest release. Please let us know if you are still having problems.
-
A "Recent Messages" Button for Comments Like on TortoiseSVN
I find the "Recent Messages" button on the TortoiseSVN Windows client extremely useful. I really miss this feature on SSC.
40 votesSQL Source Control now has a drop down next to the comment box on the commit tab, which shows your recent messages. :-)
-
Evaluate TFS Policies (Rules) when Committing DB Changes
We need SQL Source Control to comply with the policies in force for the project. eg. Checkin policies, associate with workitem policy.
57 votesSQL Source Control 3.3 now evaluates TFS policies when committing DB changes. For more information see http://documentation.red-gate.com/display/SOC3/This+commit+doesn%27t+meet+the+server%27s+policy+requirements%2C+or+the+policy+isn%27t+configured+on+your+machine.
To upgrade, use SQL Source Control’s “Help > Check for Updates…” menu item, or download directly from http://www.red-gate.com/dynamic/products/sql-development/sql-source-control/download.
-
Failed to update An item with the same key...
Failed to update:
oEc.#8Jf: An item with the same key has already been added. ---> System.ArgumentException: An item with the same key has already been added. ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 619, offset:110 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4199, offset:21 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4198, offset:578 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4148, offset:1363 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4148, offset:1098 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 4145, offset:8 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 67, offset:77 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 71, offset:40 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3984, offset:137 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 3958, offset:472 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 602, offset:614 ---> SmartAssembly.SmartExceptionsCore.UnhandledException: SmartExceptionsCore.UnhandledException @ 1792, offset:37 ---> SmartAssembly.SmartExceptionsCore.UnhandledException:
…6 votesWe think this has been fixed in v1.0. Please contact support@red-gate.com, if you are still experiencing any problems.
Thank you!
-
Is "schema.Load" as a table name causing an error?
I have just tried to link a pre-existing data database to Source Control and have come across an interesting error. Having written all the information to the source control repository it appears that the application then attempts to retrieve information back to ensure that it has the most up to date information. At this point it throws an error and points the blame at a line in my usp that is referencing a table that is called audit.Load. Is ".Load" causing the error as the software attempts to parse the file?
(I can send you the actual error text if…
6 votesThis has been fixed in the latest version of SQL Source Control.
-
Don't show conflicts when working in a Shared (Centralized) DB Model
In a dedicated db model, a conflict will occur when User1 and User2 both make a change to Table1. User1 commits the change successfully. When User2 tries to commit, they will be notified of the conflict. User2 must then decide if they want to take what's in source control or keep their version and commit this to source control. In either case, User2 may need to reapply some changes to the db and re-commit.
In a centralized db model, when all developers are working against the same db, these conflicts should NOT occur.
10 votesThis feature is included in SQL Source Control v2.0, http://www.red-gate.com/MessageBoard/viewtopic.php?t=12947.
This is a known issue in v1 because the underlying working folder is per user and is NOT shared…
NOTE: Databases linked in v1 default to dedicated databases. You will need to relink your databases to switch development models.
- Don't see your idea?