244 results found
-
Igonre create proc / create procedure commands
I have some stored procedures created in database A with the statement 'create proc' and in databse B with the statement 'create procedure'.
An option to allow me to ignore this case will very useful.
Thanks, Ésio9 votes -
Option to delete identical records from Target
Option to delete identical records from Target.
I had the need to find all identical rows and remove them from the target as they shouldnt be there. I had to use the export to CSV, and using the data generator create a table with the 81k id's and then perform a delete in sql managment studio on the temp table to delete them.
It would be so simple an usfull to be able to just select an option to delete identical rows from target in the Data compare or is there an option to control this
I can choose to…8 votes -
Support CREATE OR ALTER instead of CREATE
Sometimes, we create the migration script using SQL Comapare and schedule it for deployment. Then, it turns out, some feature has to to production ASAP, so I create the procedure there manually.
I would love the script not to fail in that case, ie. to ignore and overwrite the existing procedure.27 votes -
Colors and screen format need help
Main window which displays comparison results needs more color so differences standout. Little black boxes to indicate same, differences, left, right are not easy to quickly focus on. Must be a bug with the window sizing. Cannot size comparison results screen which spreads all content out and server/db for source and target at opposite sides of my 24' monitor. Can't size columns either.
13 votes -
Choose parts of both Source and Target side for final output to Target
My usual diff-ing tool (BeyondCompare), allows me to pick which, from a list of differences, I want to go through to a final version. I guess you might call this more of a merge-conflict-resolver than a diff-tool.
What is great about this, is that when changes have been made on both sides, I can take the 'best of both', and make sure that those go through to the final output.
Now, you might say, 'how indisciplined', to have had changes on both sides. But I've found that here, as elsewhere, absolute discipline is an aspiration, but not the answer to…
4 votes -
Memory Leak
I use SQL compare periodically as I have many clients who have the same core DB and so during development I use SQL compare iteratively to update schema, table and stored procedure changes through the 30 instances of the databases. I noticed that it progressively gets slower and consumes more RAM. Obviously I can close and restart to get a new allocation and it speeds up again. But I noticed that when starting it was consuming about 180Meg, then after maybe 15 compares the memory allocation was close to 1Gig. So something is definitely being allocated and not freed up.
6 votes -
Add Summary Details to Script
It would be helpful if the comment header of scripts generated by SQL Compare included the list of Actions present in the Summary tab of the Deployment dialog box.
We keep copies of all Production deployment scripts, but without scanning through the entire script, it can be hard to identify what is going on in each script. Having an option to include that data in the comment header would make it easier for us to track down and review what changes went out with what release.
3 votes -
Add Last Modified Date Column to Comparison Report
Add the Last Modified Date Column to the Comparison Report, like it's shown in the Application.
16 votes -
dark theme
You should create a dark theme (gray or black) UI for us who are constantly staring at your interface...
74 votes -
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…
16 votes -
Similar to other ideas, any project option to ignore should give ability not to display ignored option finds in comparison result
The project option gives you the ability to ignore based on certain filters e.g. white space. However, if any other difference is found, when you display the comparison it highlights the things you told it to ignore. If in the case of white space, every line shows a highlighted difference for a white space difference, but the one actual difference you are looking for is impossible to find without scanning the whole comparison. Ignore should give you the ability to ignore in the comparison view also (for any ignore project option).
13 votes -
SSIS package compare
I would like to suggest that SQL compare tool also have to support SSIS package compare. Currently I am at the position that I have to compare SSIS packages between two servers and find out if any SSIS packages missing plus if any SSIS packages on old version etc. Currently I am talking about SSIS packages reside in MSDB but even if it can be compare between file system, that will be great.
14 votes -
Allow changing of the tab size
In the "SQL Differences" pane, tabs are expanded to 8 characters.
(Can get very messy depending how other employees have formatted the contents of stored-procs)
Could there be a way to allow this to be customized [e.g. to 3 chars] ?
27 votes -
Ignore Database Name in Stored Procedures, Views, and Functions
We have 3 environments for one of our core applications. Each environment has a different database name: dbproto, dbuat, and db_live for an example.
We keep all the SP, Views, and Functions we develop in a separate database so at no time do we alter the database supplied by the vendor. This database name is the same in all three environments.
Because of the name difference for the vendor database all the SP, Views, and Functions are flagged as different. The only difference for 95%+ of them have is the database name (eg dbproto vs dbuat).
…
14 votes -
ignore timestamp - binary 8 differences in databases
It is an option in sql replication to map rowversion/timestamp columns to binary(8) columns. It would be a nice option for sql compare to allow for this difference between databases. Without it every table is flagged up as being different which is a headache.
9 votes -
Test for database users before creating them
For example, add an "IF" as below:
IF NOT EXISTS (SELECT * FROM sys.database_principals where name = 'xxx\yyyyyy')
CREATE USER [xxx\yyyyyy] FOR LOGIN [xxx\yyyyyy]
GO7 votes -
Add an 'Ignore owner/schema' option to SQL Compare
I'd really like this ignore option, so that [UserA].[Table] on the left hand side would match with [dbo].[Table] on the right hand side. There obviously needs to be a warning that this won't work unless table names are unique between owners/schemas (which, in my experience, they usually are).
26 votes -
The application window for SQL compare is very hard to resize...
Provide more support for resizing the app window...not the instance window ...that fine. The app window expands to the whole screen....this gives me the irrates as I need to get at stuff behind the SQL compare window
7 votes -
Allow resizing the window from a remote desktop
When remote using Windows Remote Desktop, the main application window is not resizable. The resize cursor does not show when hovering over the edges or corners, and I cannot click and drag to change the size.
17 votes -
Add a "source option" for nuget package store
It can be very useful to add an option for reading from a nuget package store, in addition to "Direct From Source Control" and "Scripts folder".
The package should be reached unsing the http url. This is useful when reading from a build server outcome, which can upload the packages to the nuget store.33 votes
- Don't see your idea?