250 results found
-
SSMS integration - compare single object
hello, i appreciate that we only need this feature because my company's processes are lacking but what I would love to have is to be able to...
right-click an object in SSMS and click an option called something like 'compare against other environment'.
it would then bring up a message box where you could browse an object-explorer for the corresponding object.
the use cases I see all the time for this are
- when people have stored procs next to each other called
spSomeProc
spSomeProcv2
spSomeProcnew
spSomeProc.oldetc on the same database.
2 when you…
6 votes -
More in-depth documentation of how SQL Compare works
Hello
It would be great if there is documentation that explains how SQL Compare works. Everything I came across so far explains what it does but I didn't find the actual internals of it. I am particularly interested in how SQL Compare handles the dependencies between various objects. For example, how can it create a view before creating the tables the view is using?
6 votes -
Be more robust in the face of Transport Errors
Data Compare almost always fails because of frequent (but short) network outages. If we could specify a long timeout, that would solve this problem.
6 votes -
Create scripts folder ignoring fill factor
File->Create scripts folder should script index fill factor. When the created folder is compared against a DB I can optionally include/exclude the fill factor as I need
6 votes -
Databases with a large amount of objects hangs
I am trying to do a schema compare and deploy but the source database has 99k objects. Is it possible to chunk the deploy feature?
6 votes -
Add Version # to your objects/DB
When running a deployment (especially for the automated DevOps part, but even for creating a deploy script) you should have the option to enter/update a new Extended Property value called like “RedGate Version #” with whatever the version number you get from the source control for that object. Ideally it would be nice to also update that in the database level Extended Property as well, but at least on whatever object you are making a change to with that deployment. That way you can self-document what the latest version control number was for that particular object (or the DB as…
6 votes -
Open only once MS SQL Server Management Studio
Instead of opening SSMS every time I create a new script with the DEPLOY button, it would be nice to check if SSMS is already openned and then switch to it instead of opening a new SSMS each time, at the end of the day I have 20 SSMS open.
6 votes -
SQL Compare should support Always Encrypted
I made a copy of a database for my application and implemented SQL Always Encrypted in the copy database. I did a compare back to the original, intending to get a deployment script to get those changes back into the original DB and SQL Compare isn't seeing the details of the columns related to encryption. I saw a message board post that indicated this isn't supported, but would like to request that support for this be added
6 votes -
Honor configured entities when running SQL Compare and SQL Data Compare from the Command Line.
Previously, when running SQL Compare and SQL Data Compare from the command line using a .scp file and .sdc file, the tool would account for the entities to be included as described in the .scp and .sdc file. At some point this behavior changed and now the command line generates a script that contains ALL differences between source database and target database. This broke our automated builds that were making use of the command line. I am requesting that this be looked at again, and that these tools would take into account the entities described in the .scp and .sdc…
6 votes -
allow partial name search in database name
When selecting a database name, please allow filtering the list by typing partial strings from the middle of the name of the database name. for example, if my database name is "Database_1335" I could search for it by typing 1335
6 votes -
constraint
Make 'Ignore Constraints' ignore default constraint values.
6 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 -
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 an option to ignore the Unicode differences in Extended Properties.
Add an option to ignore the Unicode differences in Extended Properties. SQL Compare currently will differentiate between Extended Property text (e.g., for MS_Description) created as Unicode vs Ansi (e.g., N'My text' vs 'My Text'). SQL will apparently maintain this different even though scripts generated from SSMS always show it as Unicode (with N). Thus, this can cause SQL Compare to show differences between two databases where there is none intended (the description text is identical).
5 votes -
Make SQL Compare easier to use across many database projects by allowing saving project options and filters as template
Each of our production SQL servers has dozens of databases on it. We have a SQL Compare project file for each database to compare it between the production and dev servers.
Sometimes we find out that we've been using different comparison settings (either filters or project settings or both) between databases that results in us not finding differences that we should have, in hindsight, found.
It'd be super if there were a way to define the filters + project settings by at a higher level, and perhaps tied to either the database name, the source server, or the target server.…5 votes -
Option to ignore preserving data when adding a NOT NULL column to a table
SQL Compare tries to preserve data from table when adding a new NOT NULL column and adds below steps to deployment script:
1. Create a new table B with same structure from original table A
2. Perform INSERT INTO table B SELECT * FROM Table A
3. DROP Table A
4. Rename Table B to Table AThe issue:
For example if we add a new column to a ETL table with 1M rows. We don't need data to be preserved since table gets populated during ETL process. The deployment script without manually remove INSERT statement will take a very…5 votes -
Include new functions, views and stored procedures in "use DROP and CREATE"
Would like to include newly defined views, functions and stored procedures when dropping objects in deployment script. Currently, if you create a new stored procedure, then do the compare, it only does a CREATE in the script even if you have "use DROP and CREATE" selected as an option. I have to manually add the drop commands to the script so that it can truly be executed multiple times if needed.
5 votes -
select what to compare
On the same screen as specifying the databases to compare, I'd like to specify what objects (tables, procs, functions, ...) should be compared and have the choices saved with the project. Often, I'm looking to see whether I made an update to an object in DB2 that I made in DB1 and I don't need/want to wait for all objects to be compared. Sort of using the object filter ahead of time.
5 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 -
Add "use <<Database>>" as an option in SQL Data Compare
This option exists in SQL Compare but not SQL Data Compare.
4 votes
- Don't see your idea?