587 results found
-
Integrate with IBM Rational Team Concert
Any plans to integrate with IBM Rational Team Concert?
23 votes -
Support change data capture (CDC)
When enabling change data capture on a database, source control does not pick up the system tables created, nor the changes to the database configuration. It is only able to gather the schema, role and function changes
22 votes -
Support SQL Azure for large database development
I know you already declined another request to support SQL Azure on the grounds that you do not recommend using SQL Source Control on a production database, but please reconsider supporting SQL Azure for development.
22 votes -
Analysis Server (SSAS)
Support for Analysis Services Databases
21 votes -
Check and Commit Changes over all Databases
Checking for Changes should be possible over multiple Databases on a Server. All Changes on a Databaseserver should be allowed to commit at once.
21 votes -
Force "Get Latest" even when tool thinks there are no changes.
Our test environment is set up such that the servers and databases all have the same name as production. This causes SQL Source Control to think I'm connected to ServerA when I am really connected to ServerB. Thus, the "Get Latest" tab shows "No new changes in source control" even though there are changes I wish to get. The "Commit Changes" tab still shows changes so the tool knows there are differences, but won't show any "Get Latest" items. This happens in both the "Dedicated" and "Shared" setups. I must unlink the database and relink it in order for it…
20 votes -
Commit data and schema changes separetly
A table is under source control and the data of that table is linked as static data.
Both table definition and data has been changed and are visible in the 'Commit changes' tab.
Since the data is just edited and changed for development purpose it should not be committed.
But in this situation it is impossible to only commit de table definition.
When checking the table the data is also checked (and the other way around also).It would be nice to be able to commit the changes separetly.
20 votes -
Source Control - Changed by unknown
Problem:
Sysadmin role is required to see who changed a DB object. I am not permitted to have this role and I would imagine many devs are in the same boat. This means that when many objects have been checked-in by many users it is hard to pick out one’s own changes.
Solution:
Have an option when checking-in which adds a 1 line encrypted comment to the start or end of each object script. The comment would contain the username of the person making the check-in (and a control parameter like the time of check-in for instance)
This username can…20 votes -
Generate a Script rather than Apply changes in the Get Latest tab
I am using GIT and SQL Source Control. After running "Pull from remote repository" in the Get Latest tab, the only option is to Apply changes which directly updates the database.
If the changes include something like the classic renaming of a column, it will drop the column and add a new one and I lose data.
I would like to be able to simply generate a script so I can review it and manually apply it rather than directly update the database.
20 votes -
Schedule commit
Ability to schedule that changes are committed daily/weekly/...
19 votes -
Automatically commit changes as they are made
It would be nice to be able to automatically commit changes in the background when an object is created or modified.
19 votes -
Allow an option to exclude members of database roles from SSC.
We like to control access to objects using database roles. However, the members of the roles are different in different environments (dev, test and live). I want to include the roles (and their permissions) in SSC, but don't want SSC to worry about the members of the roles - this can be handled manually.
19 votes -
Keeping history of locked and unlocked objects
Locking feature doesn't keep history of who has locked or unlocked specific objects in database. This could become useful when a person unlocks an object locked not by him/her and would help to track historical changes.
It would require very few changes - additional history table,
[SQLSourceControl].[LockObject] and [SQLSourceControl].[UnlockObject] procedures would have to be modified.
Possibly an additional view to see that data in SQL Source Control instead of selecting raw tables.
19 votes -
Add ability to Merge Static Data
"Take theirs" and "Keep mine" are an all or nothing option, I would like to have more control over this and be able to keep my new records but take the updated, or keep my updated records but take the new records, for example.
19 votes -
Add % Progress indicator to "Calculating Changes" & "Determining Latest Version"
When dealing with big Databases (100's of tables, views, sp's etc) "Determining Latest Version" and "Calulating Changes" can take ages, you cant navigate away to another database because the Source Tab restarts on the new database. If you cant speed this up, a progress indicator would be helpful when working on multiple databases and multi-tasking.
18 votes -
accurev
I'm missing native support for AccuRev (http://www.accurev.com/) in the SQL Source Control product.
18 votes -
When committing, show when multiple people have edited an object
When comitting:
Andy makes an edit and "Changed By" shows "Andy" (but does not yet commit).
James then makes an edit and "Changed By" is now "James", but does not mention "Andy"It would be useful if it could show "Andy, James", to highlight a potential conflict.
18 votes -
Make SQL Source Control external to SSMS
Make SQL Source Control external to SSMS like SQL Compare. This would allow the developer to use what ever IDE they want to and still commit the changes the same way. I would use SQL Compare to make changes, but it can't do everything SQL Source Control can. Mainly the migration scripts and the pre and post scripts.
18 votes -
ComparisonOptions.xml should be easily shared and checked-in for each project
Having to set up as described in the link below isn't very nice at all.
http://documentation.red-gate.com/display/SOC3/Setting+SQL+Compare+options+in+SQL+Source+ControlThis should be a standard (easily-accessible) setting that you can have on a per-project basis (not a per developer basis) so that you don't have to worry about individual machines.
17 votes -
object_schema_name
Bug: the function objectschemaname is not recognized as a valid system function, and is wrapped in [] when committed to subversion backend. Scripts defining tables or stored procedures that use this function have to be edited to remove the [] before they can be successfully run. Please fix this, this is a function we put into almost every table as part of the default value in a "created by" field.
17 votes
- Don't see your idea?