53 results found
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
It would be mint* to be able to have SQL Server Maintenance jobs included in SQL Source Control. Could it be added as a new feature?
- (see kid from Super8 movie)
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
Most of our enterprise applications have mutiple instances of the same DB schema. We use the shared model and would like to update al instances once we commit changes on one of them. As a workaround we commit the changes and then hit revert changes on the instances we need to update70 votes
Commit dependencies dialogue shows blue dot on objects even when those objects have no changes to commit. This seems incorrect.3 votes
If there is a new Filter available at the moment this gets listed in the Get Latest tab with all other objects. Really you should apply this first before committing changes or getting latest. If you don’t there’s a danger you commit or get objects that should be excluded by the filter.
For example if a new filter excludes Users and Roles, but you fail to synch this before committing latest you can easily commit recently created users and roles that should simply have been excluded.1 vote
Be able to apply the SVN Relocate command. I often switch between our SVN server while on the LAN, but then when on the road I connect "relocate" to the SVN server using external IP address of the server using the SVN relocate command.1 vote
We use the shared database development model and can have several projects going at once. Some developers may jump back and forth between projects. It would be nice to have the ability to setup a single database connection to multiple branches. Possibly using the SSMS registered server name instead of the physical server name.39 votes
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 and any user can commit any other user's changes. It would be nice if an administrator setting could be set that would only allow users to commit their own changes There should be someway to prevent other users from committing your changes.79 votesKendra responded
An update for users on the status of this suggestion:
An ‘object locking’ feature was added to SQL Source Control following the creation of this item which can helps users working in a shared database environment not write over each other’s changes.
This may help prevent accidental commits in some cases, as there is a “Locking” tab which allows users to see which other users are working on specific items.
Locked items are still eligible to be committed, however, and there are cases where users will want to commit an item — perhaps to a specific branch in source control which is not ready to deploy — even if the item in the database is locked.
We have found at Redgate that the easiest way to enable alignment with distributed source control systems such as Git is to empower users to use dedicated development databases rather than shared databases. Tools…
We occasionally restore a copy of production db over our development db. With SCC in place I imagine it will work like this:
1) Everyone commits dev changes that they care to keep
2) perform restore
3) One person relinks SSC in dedicated mode and uses "get latest" to pull down latest schema to the newly restored dev db.
4) everyone can resume working in shared model.
To cut out the relink in step 3, it would be nice to be able to use the "Get Latest" tab in shared model for occasions like this34 votes
Similar to how fortress works with visual studio. All objects in the database would require an exclusive or shared lock to be worked. If an object is changed without a lock it becomes renegade for that user.8 votes
- Don't see your idea?