249 results found
-
Support for Replicated Databases
I would like to push schema changes to a transactionally replicated database. Now, SQL Compare breaks replication when I push schema changes. Please add support for sprepladdcolumn and sorepldropcolumn rather than ALTER TABLE.
117 votes -
Make SQL Compare Three-part identifiers aware and filterable
Not always a deployed database has the same name of the source database due to customers' naming conventions. So it'd be great if SQL Compare will be three-part identifiers aware, so that if you compare the same table from different named databases as following:
SELECT *
FROM MyDatabaseA.MyTableSELECT *
FROM MyDatabaseB.MyTableSQL Compare will not show them as different if you want a three-part identifiers insensitive comparison.
18 votes -
137 votes
-
Compare tab contents!
I have yet to find a tool to compare the contents of two tabs in SSMS.
Ideal would be the ability to run an executable on the temfiles of two tabs. So the user could use diffmerge or whatever they liked, But any diff-function would be greatly appreciated.I don't know if SQL Compare is the right place, but it could be.
4 votes -
Compare instance level information
Like configuration settings, security info (logins, server roles...), linked servers, jobs, SSIS catalog info for SQL2012 (folders, environments, security, projects, packages...) etc.
42 votes -
Ability to Compare from a dacpac to a Database and generate sync scripts
I understand that you have the ability to compare DBs to sqlproj but it would be nice to have it compare with a dacpac. That way I can build a project, persist that build number and deploy from that dacpac.
6 votes -
Ability to selectively ignore column defaults
I'd like to be able to compare two databases, yet ignore certain column defaults in my comparison
20 votes -
Allow SQL Compare to ignore difference due to ALTER and CREATE
When comparing a VS 2012 database project to a database, when the only difference is ALTER vs. CREATE (which happens because a stored procedure ALTER was executed directly, then saved) the comparison fails. An option to ignore this difference would be very handy.
9 votes -
Reuse Open SSMS for deployment scripts
When selecting the option to open the deployment script in SSMS Compare opens a new instance of SSMS for each script that you generate.
In place of that would it be possible to open the scripts in an existing SSMS instance that is open already? This would make things a lot easier when generating multiple scripts.
35 votes -
Add "use <<Database>>" as an option in SQL Data Compare
This option exists in SQL Compare but not SQL Data Compare.
4 votes -
Add option to stop processing if the database in the USE statement doesn't exist
If you run a script with option to use the "USE database" clause and the database doesn't exist the script will go ahead and attempt to run the script in the current database. This is usually "master" if you are in a new query window and if you only adding new items it will add them all to the master db.
5 votes -
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.
103 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.
108 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
- Don't see your idea?