- or
23 results found
-
New Option to Ignore Statistics_Incremental
I would love to have the option to ignore the StatisticsIncremental setting on indexes much the way "Ignore StatisticsNoRecompute" works. I currently have two DBs - one has this option on all indexes and one has it on none. Currently SQL Compare flags all indexes as different even with "Ignore Statistics" turned on. The only option is to ignore Indexes entirely which isn't practical because those are the most frequently changing objects between the DBs. I'm currently still using SQL Compare 10 because it does not pick up the Statistics_Incremental option but I would love to be able to upgrade to 12 if it had the option to ignore this setting. Thanks!
I would love to have the option to ignore the StatisticsIncremental setting on indexes much the way "Ignore StatisticsNoRecompute" works. I currently have two DBs - one has this option on all indexes and one has it on none. Currently SQL Compare flags all indexes as different even with "Ignore Statistics" turned on. The only option is to ignore Indexes entirely which isn't practical because those are the most frequently changing objects between the DBs. I'm currently still using SQL Compare 10 because it does not pick up the Statistics_Incremental option but I would…
16 votes -
Add Summary View command line option
Currently there are 3 output options when running sql compare via the command line /quiet /verbose and the default. I'd like to see an option between the default and verbose logging similar to the "Summary view" present in the main application.
For example: I'd like to see the tablename that has diffs (default option) AND the name of the index on said table that is different (new summary option), but not the entire table definition (verbose option).1 vote -
Avoid creation of Recovery tables
Please give an option to ignore Recore tables creation. I am trying to use SQLCompare in DevOps model to avoid long release timings. But if there is any data type change to a huge table then current concept of creation of recovery tables is disabling all the FK's, removing indexes and eventually creating a new table. This is very long process and not benefitting the projects. There should be an option to avoid the creation of Recovery tables. Please think in that perspective.
16 votes
245 results found
-
constraint
Make 'Ignore Constraints' ignore default constraint values.
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 -
excel
Include attributes to be changed in an object to an excel report in sql compare. include not only the object name to be changed but the actual change to fields
within the object or the script change to be made for programability items users roles and permission. e.g. Database.schema.objectinsource.change(details of change column to be altered in a table its original value its new value its datatype and length its nullability and any default constraints.1 vote -
Allow filters to be case INsensitive
Allow filters to be case INsensitive
When I add a filter e.g. schema name begins with "ABC" then objects with schema Abcdef will not be shown even though i have opted for case insensitive matching
this means that I have to make several OR filters to cover all combinations of upper or lower case letters1 vote -
Commented-out blocks of code should show as changed
When an entire block of code is commented out with the /* */ characters, SQL Compare only shows only the lines with these characters as changed. It does not show the unchanged block of code between them as changed, even though the impact of commenting out this code can indeed be a significant change.
I suggest that unchanged lines of code enclosed by /* */ around it should still show as a substantive change. When we recently deployed an SP update with a large block of code that was commented out during testing, it slipped in because the scrolling view that shows where the changes are registered very small changes and it was overlooked.
When an entire block of code is commented out with the /* */ characters, SQL Compare only shows only the lines with these characters as changed. It does not show the unchanged block of code between them as changed, even though the impact of commenting out this code can indeed be a significant change.
I suggest that unchanged lines of code enclosed by /* */ around it should still show as a substantive change. When we recently deployed an SP update with a large block of code that was commented out during testing, it slipped in because the scrolling view…
1 vote -
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 files.
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 -
ned.bush@ky.gov
Have pop-up screens (My Projects, Compare Progress, Save Script, etc.) open up on the same display as the main program when program is running on a computer with multiple displays.
I've noticed that if I'm running SQL Compare or SQL Data Compare and move it to my secondary display, it still tries to open up pop-up dialogs on the primary display. This can be annoying, especially if it has been a little while since I used the program and I forget it does this and can't spot why program seems to have stopped responding to mouse clicks. Also, when the displays are different sizes (larger monitor attached to a laptop, etc.) the pop-up position can be awkward (have to move pop-up to see buttons, etc.)
Have pop-up screens (My Projects, Compare Progress, Save Script, etc.) open up on the same display as the main program when program is running on a computer with multiple displays.
I've noticed that if I'm running SQL Compare or SQL Data Compare and move it to my secondary display, it still tries to open up pop-up dialogs on the primary display. This can be annoying, especially if it has been a little while since I used the program and I forget it does this and can't spot why program seems to have stopped responding to mouse clicks. Also, when the…
1 vote -
1 vote
-
Allow option to not script logins when generating script and also add check for existing users to avoid errors
I was trying to create a copy of the development DB schema into local server. I got errors and warnings. The error I got was in the section of code that created the login and then attempted to create a user (myself). I didn't sent this error as it contained some confidential info. There also needs to be a way to remove things like login names from the generated email.
1 vote -
Correct order when renaming column and adding column with the old name
After explicitly fixing column mapping, I encountered an error when renaming an existing column and then adding a new column using the old name (different casing).
SQL Compare had scripted the column add before the rename.
SQL Compare needs to be able to detect the conflict and script the rename before the column add.1 vote -
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 -
Reports created with /ReportAllObjectsWithDifferences should indicate filtered items
I had a panic moment after forgetting that the /rad option was added.
The report made it look like all production users had been removed!Please change the color to a lighter or darker shade and add a "filtered" icon with tooltip that clearly explains that the change was not applied due to filters or exclude/include commandline options.
Kids, don't play tricks on your peers with this option!
3 votes -
Enhance 'Force Column Order' to 'Force Column Numbers'
Sometimes tables can differ in system column metadata (sys.columns) even if they looks completely identical - for example, if I drop a column in a middle of a table. After copying the table to another DB a column id for a half of columns will be different. But some frameworks or applications we use, rely on it, and require reconfiguration / rebuild even on a such a minor change.
It will be great to have a feature 'Force Column Numbers' to preserve column id's for table or view on deploy.3 votes -
3 votes
-
Decrypting object performance (batch DBCC PAGE calls)
I frequently need to "generate scripts folder" against large (10k+ objects) databases including encrypted objects (thousands of encrypted stored procs).
A recent run on a (50ms rtt) vpn link took 2+ hours to complete.
It appears that object decryption performance appears to be bottlenecked on
performing 3 round trips to read a single db page, specifically:batch 1: dbcc traceOn(3604)
batch 2: dbcc page(DB, 1, 6573692, 2)
batch 3: dbcc traceOff(3604)
batch 4: dbcc traceOn(3604)
batch 5: dbcc page(DB, 1, 6573694, 2)
batch 6: dbcc traceOff(3604)I think batching page reads (and eliminating many traceon/traceoff commands) would make object decryption performance much better, especially over higher-latency links:
batch 1:
dbcc traceOn(3604)
dbcc page(DB, 1, 101882422, 2)
dbcc page(DB, 1, 101882423, 2)
dbcc page(DB, 1, 101882496, 2)
dbcc page(DB, 1, 101882497, 2)
dbcc page(DB, 1, 101882498, 2)
dbcc page(DB, 1, 101882500, 2)
dbcc page(DB, 1, 101882501, 2)
dbcc page(DB, 1, 106085028, 2)
dbcc page(DB, 1, 105837684, 2)
dbcc page(DB, 1, 114755183, 2)
dbcc traceOff(3604)Attached is an annotated pcap screenshot showing the 3x RTT latency per page read.
I frequently need to "generate scripts folder" against large (10k+ objects) databases including encrypted objects (thousands of encrypted stored procs).
A recent run on a (50ms rtt) vpn link took 2+ hours to complete.
It appears that object decryption performance appears to be bottlenecked on
performing 3 round trips to read a single db page, specifically:batch 1: dbcc traceOn(3604)
batch 2: dbcc page(DB, 1, 6573692, 2)
batch 3: dbcc traceOff(3604)
batch 4: dbcc traceOn(3604)
batch 5: dbcc page(DB, 1, 6573694, 2)
batch 6: dbcc traceOff(3604)I think batching page reads (and eliminating many traceon/traceoff commands) would make object decryption…
3 votes -
Separate ifg in the SQL Compare Options
Please break out the ifg switch in SQL Compare Options so file groups are separate from partition schemes and partition functions. Maybe ifg only ignores file groups, and create a second name ifp (or whatever) that would ignore only partition schemes and funtions.
1 vote -
Database scoped credentials are missing
SQL Compare ignore database scoped credentials. So you wont be able to create external data source from generated script. It's clear that password is not accessible. But if you prepare create statement with data available from sys.databasescopedcredentials and let us fill out secret it will be much better then to skip this object.
1 vote -
Left justify both Object Name columns
We prefix our objects with certain characters, so to right-justify the left Source "Object Name" column names makes it hard to visually read down the list of objects to find something in particular.
3 votes -
Rebuild partition instead of dropping & recreating primary key when only changing data compression
SQL Compare currently attempts to drop and recreate a primary when changing compression.
REBUILD PARTITION ALL WITH (DATA COMPRESSION PAGE|ROW|NONE
would be more efficient and less intrusive since, among other things, it doesn't require dropping and recreating all foreign keys.2 votes -
Synapse Compatibility
Can the compare engine be enhanced to work with Azure Synapse?
12 votes
- Don't see your idea?