Comments
Sort by recent activity
Hi @Pete H / comments
Hi @Pete H
I've just run through this to double check, and it looks like the bug reference Mike (EDIT, sorry, *Alex*!) mentioned (SOC-6031) is indeed the correct one. The behaviour is the same when linking to the .sqlproj folder.
I'm not sure right now when we're working on improving compatibility with ssdt projects, but when we do, this should be on the list of things to tackle. / comments
I've just run through this to double check, and it looks like the bug reference Mike (EDIT, sorry, *Alex*!) mentioned (SOC-6031) is indeed the correct one. The behaviour is the same when linking to...
The latest frequent-update version of SQL Source Control (4.0.6.179) allows you to default the checkbox behaviour to off. To do this, you'll need to edit your UI Options file (RedGate_SQLSourceControl_CommonUI_UIOptions.xml) which you'll find in %localappdata%Red GateSQL Source Control 4 and add a tag called IncludeDependenciesCheckbox, like this:
<IncludeDependenciesCheckbox>False</IncludeDependenciesCheckbox>
If the value is false, then the checkbox will be un-set by default. Note that a restart of SSMS is required for this change to take effect.
You should still review the dependencies shown, to ensure that you don't commit changes that would break the database for other users who then "Get Latest". / comments
The latest frequent-update version of SQL Source Control (4.0.6.179) allows you to default the checkbox behaviour to off. To do this, you'll need to edit your UI Options file (RedGate_SQLSourceCont...
Just to follow up on this, we recently released object locking as a beta feature in our latest Frequent Updates release. To get this, go to Help > Check for Updates and turn on Frequent Updates in the configuration option. / comments
Just to follow up on this, we recently released object locking as a beta feature in our latest Frequent Updates release. To get this, go to Help > Check for Updates and turn on Frequent Updates in ...
Just to follow up on this, we recently released object locking as a beta feature in our latest Frequent Updates release. To get this, go to Help > Check for Updates and turn on Frequent Updates in the configuration option. / comments
Just to follow up on this, we recently released object locking as a beta feature in our latest Frequent Updates release. To get this, go to Help > Check for Updates and turn on Frequent Updates in ...
Hi,
You shouldn't need the use dbname statement in the scripts that are source controlled. In fact adding this is more likely to cause problems (for example if your development DB is called workDb, you commit everything, and another user tries to "get latest" the changes into a db called testDb) - the scripts in the repository are never intended to be manually run; they are simply a representation of your database.
I'd be curious as to the use-case you have where the database name setting would be helpful? / comments
Hi,
You shouldn't need the use dbname statement in the scripts that are source controlled. In fact adding this is more likely to cause problems (for example if your development DB is called workDb,...
Thanks for your post.
Unfortunately there's no option to save the scripts as you describe.
The reason for this is because we don't ever intend the scripts to be run manually. Instead, they are there to represent a state of the database at any given time. To execute the scripts against another database, you'd actually use a tool such as SQL Compare to deploy the database. This works by comparing a model of your database represented by the scripts against the target and building a migration script to move from one state to another.
SQL Compare does offer an option to use drop and create instead of alter in the deployment scripts it generates, but that won't affect the ones you have held in your repository by SQL Source Control. / comments
Thanks for your post.
Unfortunately there's no option to save the scripts as you describe.
The reason for this is because we don't ever intend the scripts to be run manually. Instead, they are ther...
Incidentally, while we look into this, a slightly quicker way to get the revision rather than waiting for the history screen to load would be to right click your DB, select Properties, then Extended Properties. You'll see the revision listed there. / comments
Incidentally, while we look into this, a slightly quicker way to get the revision rather than waiting for the history screen to load would be to right click your DB, select Properties, then Extende...
Yes, newer versions we recommend you restart SSMS between an unlink and relink, otherwise it may relink to the same files and not help fix the problem / comments
Yes, newer versions we recommend you restart SSMS between an unlink and relink, otherwise it may relink to the same files and not help fix the problem
I'm surprised you're seeing the error about duplicates- normally the first error (about the missing SharedSSMS file) would stop SQL Source Control loading.
I'd suggest running a "repair" of the SQL Source Control installation from the add/remove programs option in Windows to see if that fixes the first error. For the second error, try unlinking your database, restarting SSMS and then relinking. That may well fix it, but if not, please email our support team (support@red-gate.com) with details of the error (send in the error report with your email address when prompted as well) and they'll be able to help out. / comments
I'm surprised you're seeing the error about duplicates- normally the first error (about the missing SharedSSMS file) would stop SQL Source Control loading.
I'd suggest running a "repair" of the SQL...