238 results found
-
Add a Rollback Script Save option for both SQL Compare & Data Compare
In order to create a rollback script, we currently need to reverse the direction of deployment, save the rollback script, cancel the deployment, change the direction, then proceed with deployment in the correct direction. It would be great if the same screen on the Deployment Wizard would allow you to save BOTH a change script and a rollback script.
99 votes -
Choose source control label as a version of a data source
Today, SQL Compare allows for two options when selecting a version of a source control data source - latest (head), or any other change set. It would be great if there was a third option: to select a version by label. We use labels as a means for controling which code is promoted from development to test to production. Anything ready to promote is labeled as “build ready.” It would be great to use this build ready label when selecting the version from the repository.
57 votes -
Compare (and migrate) Database Diagrams
I'd love to see a function in SQL Compare to compare and migrate Database Diagrams. Especially between servers, but certainly on the same server.
We use them all the time to work on the structure of the of our databases and I'd love to be able to see the same diagram when I'm working in Prod and Test as I do in Dev without having to bring the changes across manually.
The code (for the easy case) is pretty simple.
UPDATE MyDB.dbo.sysdiagrams
SET definition = (
SELECT definition
from MyOtherDB.dbo.sysdiagrams
WHERE name = MyDB')
WHERE name = 'MyDB'17 votes -
Compare against Database Projects
It would be great to see SQL Compare support Visual Studio Database Projects (.sqlproj).
Current if you choose Source Control | Scripts, you can point to the project folder, but then SQL Compare gets confused because it loads in extra .sql files (eg. the 'create database'.sql that gets put in the build output 'bin' folder).
Selecting the 'Tables' sub-folder works more reliably (if just comparing tables!), but then pushing changes down to the files results in schema that no longer compiles because the SSDT tools require 'GO' separators between each DDL statement.
5 votes -
Sync a Database to a Source Control Repository
We really need the ability to "sync" a database to VCS repository, not just compare. I know this limitation exists by design because conflicts can be missed, but we have a scenario that demands it. We have batch check-ins that can take up to a half a day to commit manually.
10 votes -
Include tables in "use drop and create instead of alter" comparison behavior
Provide additional option to "use drop and create instead of alter" so that tables can be reconstructed blindly
32 votes -
Ignore DEFAULT(X) column constraints
Replicated (push) tables do not contain default column constraints on the subscriber which are identified as breaks within SQL Compare 10. Provide the ability to ignore DEFAULT(X) properties on column within the UI.
99 votes -
Add BACPAC to SQL Compare (and SQL Data Compare)
At the moment you can compare Database, Backup, Snapshot and Source Control.
Please add a BACPAC file as well.
A BACPAC is an artifact that encapsulates the database schema as well as the data stored in the database. The BACPAC is a Windows file with a .bacpac extension. Similar to the DACPAC, the BACPAC file format is open – the schema contents of the BACPAC are identical to that of the DACPAC. The data is stored in JSON format.
How to: Import and Export a Database (Windows Azure SQL Database)
http://msdn.microsoft.com/en-us/library/windowsazure/hh335292.aspxImport a BACPAC File to Create a New User…
88 votes -
Drop
Add an option to DO NOT DROP missing fields in the target, this way I'm just adding missing fields from the source.
16 votes -
BUG: Filter Rules do not apply to triggers.
We're using MS Data Sync Services which makes heavy use of versioned tables and triggers to populate these tables. The objects are named x.x.x.xTableName (example 1.0.0.13Table and 1.0.0.13Tabledeletetrigger. The triggers to populate these objects are placed on the base table (TableName, not x.x.x.xTableName).
To create deployment scripts, I utilize filter rules to remove table names, stored procedures, UDDTs, etc. used by Data Sync Services. However, the DSS triggers placed upon the base table are still scripted out; they are not filtered out as I would expect.
P.S. For those thinking of using Data Sync…
4 votes -
Option to select individual dependencies (or affected objects) when migrating changes with the deployment Wizard.
Currently the Deployment Wizard only allows for all dependencies to be specified, or not. If I know a specific dependency to be problematic (will fail the overall deployment if selected) my only options are to not deploy dependencies (not good) or to generate a migration script and step through it a bit at a time or remove references for the dependencies I need to skip, which can be cumbersome when dealing with many changes. It would be nice to be able to choose all dependencies (current option), specify not to deploy dependencies (currently an option), or incrementally check on or…
74 votes -
38 votes
-
filter
In SQL Compare make it remember the filter you last choose.
I set up my filters and saved them to a file. Then picked that file in the filter drop down.
The next time I bring up SQL Compare, I have to pick the filter again from the drop down. SQL Compare should remember the last one I used. Or give me the option to remember it like The Project Options allow you to save as My Defaults.
8 votes -
When tables have different number of indexes the compare will show differences when in reality the indexes are the same, just not aligned.
A table on server 1 has 2 indexes. The same table on server 2 has 4 indexes. Depending on the order that the script generates the DDL the compare might show all 4 indexes as different/new where it should show 2 as the same and 2 new.
87 votes -
Allow comparing objects of all types with different names, not just tables.
It would be nice to be able to use RGSC to compare such objects by re-mapping. A recent change allows doing this, but with tables only. All other objects would be a helpful touch.
This could be useful for several scenarios, including demonstrating a proposed change to a current version. We also sometimes end up with different test versions of objects that differ slightly with less than helpful comments. (b/c all our devs' code is self documenting!)42 votes -
Option to script indexes and triggers into their own sub-folders
Project level option to script indexes and triggers into their own sub-folders. This allow for a more granular check-in and makes text diffs more clear.
37 votes -
Pull filter from source controlled database
When comparing a source controlled database (SSC) to a live database, it would make sense to use the source controlled database's object filter (filter.scpf file) when running the comparison instead of having to manually recreate the filter inside of the SCP project. Also, it would be better if the SCP project stored a link to the filter file used instead of storing the filter string, as it is very inconvenient to have to maintain these separately. If the filter file is changed in SSC, I want SCP to be able to pick up the change automatically.
11 votes -
Color-coding servers
For safety when moving among servers, I have the desktop backgrounds of my servers color coded as follows:
My workstation - green
Other developers' workstations - blue
Development - yellow
UAT - orange
Production - redIn SQL Server Management Studio, I've colored the status bar for any query window in the corresponding servers the same way.
It would be nice if I could color-code the two halves of the "compare to" window in SQL Compare and SQL Data Compare the same way, based on the server/instance name!
Even better, could it pull the color values from some SQL Server…
76 votes
- Don't see your idea?