587 results found
-
Items removed from the DB aren't indicated as a DB change by the SSMS GUI.
No Category for BUGS? When comparing the TFS version to live DB in SSMS, objects missing from live DB don't cause the "change" visual queue. One must select the DB/SQLSource Control/Get Latest Tab to realize there are extra items in the DB. SQL compare does not have this issue.
3 votes -
Support Filetables with Fulltext-Index!
I Need it so badly. Having a Error in every view of the GUI because of it
1 vote -
Amending last commit
We use SQL source control linked to Gerrit. It would be really useful to be able to 'Amend last Commit' inside the GUI.
4 votes -
15 votes
-
Get Latest: Error: Show the script involved to give a clue where the error is located
When you hit get latest and your stored procedure contains an error, it fails to get the latest. It doesn't give a clue in which piece of code the error is located
1 vote -
Allow ability to ignore specified object(s) by database
Most objects are shared among our several databases, while some only apply to some (or only one) of our databases. Add the ability to ignore objects by database by right-clicking the database object and clicking a menu item like "Ignore this object in this database" and/or "Ignore this object in all databases except this database". So then we don't need to have an object in one/many of of our databases that is not used in that database(s), source control would not show the need to be updated or added because it is on the ignore list for that database.
4 votes -
Unlinking database from source control takes forever
When I unlink the database from redgate source contriol SSMS does not respond and it takes more than 10 mins to do.
6 votes -
Add the "solution" concept for multiple projects
It would be nice to allow comparison "solutions" where you could have multiple projects bundled together. The solution comparison could be run in a single step, and all projects would be run with results in separate tabbed windows. For example, on a weekly basis I need to compare DEV and LIVE schemas for nine databases. I have nine separate projects that I need to open and run. If I could bundle these into a solution, run the solution and have all nine projects run and get their results displayed in tabs, that would save a ton of time.
8 votes -
1 vote
-
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 -
Removing column does not generate update in static data
If a table is setup for static data, and you remove one or more columns from that table, the static data is not updated in the working directory when "Saving changes".
7 votes -
Deploy to database without preserving data
am trying to deploy changes to tables from one database to another as part of development. SQL Compare insists on creating temporary tables in the target database, putting the data in them, and then trying to insert the data back into the new tables (which now have different types/names for columns).
I cannot find an option to turn off the preservation of existing data.
I want to deploy my schema changes while discarding any existing data if present. (It is called SCHEMA compare after all)I don't understand why there isn't an option to ignore data currently in target tables…
3 votes -
It would be great to see the changes before they are commited to the source control
This would be a comparision between the local version of the files (e.g. loaded from the database) with the latest release on the version control system.
1 vote -
Indexed view definitions don't compare with latest version properly
When comparing view definitions from local objects to latest source control version (perforce in our case), SQL Source control doesn't properly read the data compression options from the source control version. So we'll get a difference, showing "WITH (DATA_COMPRESSION = PAGE)" highlighted orange on the left....however the source control file also has this clause, it's just not being read properly. If I check in the file, it will refresh and the same object will still show a difference with source control, even though it's not.
4 votes -
Filter and Comparison Options should *always* show on top if not in sync.
It's far too difficult to find the Filter and Comparison Options items if there are lots of things that might be filtered out or excluded via options. These items should always show on top regardless of the UI sort order because they are so important to synchronize first.
7 votes -
Set default options for comparison
Allow use to set default comparison options e.g. <AddDatabaseUseStatement> rather than have to do it for every individual database linked.
5 votes -
Would love to see a feature that ignores any local changes and allows you to simply bring the local database up to the latest version
We often restore databases into our working folder and would love an option to simply bring that database up to the latest source controlled version. Right now when we restore a database Source Control thinks we made a bunch of changes so we end up having to "undo" those changes.
29 votes -
SQL errors when constructing temporary database should show failing script
On creating a new migration script (Migrations V2) and switching to the "Commit changes" tab, an error in an unrelated object (e.g. stored procedure referring to a non-existent column) causes SQL Source Control to fail with "An error occurred while creating a temporary database". The complete error message shows a stack dump, originating with the error in the script which has been run to create objects in the temporary database.
It would be much more helpful if SQL Source Control recognised that an error has occurred in the script and make the script available for viewing, similar to the way…
1 vote -
6 votes
-
5 votes
- Don't see your idea?