Comments
Sort by recent activity
The repro steps don't exhibit the problem in this patch build: ftp://support.red-gate.com/patches/SQL_ ... 2.0.28.zip / comments
The repro steps don't exhibit the problem in this patch build:ftp://support.red-gate.com/patches/SQL_ ... 2.0.28.zip
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...
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...
I don't believe it's possible to default this to being unchecked.
Out of curiosity, what's the reason behind not committing dependencies? Not doing so increases the likelihood getting the repository into a state where other developers cannot retrieve changes (for example if you create a couple of new tables linked by a FK, but only commit one of them (saying no to dependencies), Get Latest will fail for other users when we try to create the FK, as the other table is missing) / comments
I don't believe it's possible to default this to being unchecked.
Out of curiosity, what's the reason behind not committing dependencies? Not doing so increases the likelihood getting the repositor...
Hi- the undo option is really intended for database changes. I'm not sure as to the exact reason why we don't allow that with filters unfortunately.
Asides from simply re-configuring the filter, you might also find that unlinking and then relinking will show up the filter on the Get Latest tab so you can pull the change down from your repository / comments
Hi- the undo option is really intended for database changes. I'm not sure as to the exact reason why we don't allow that with filters unfortunately.
Asides from simply re-configuring the filter, yo...