SQL Compare and SQL Data Compare are great. PostgreSQL is a great database - and one that seems to be gaining increasing traction. We're wanting to increase our usage of PostgreSQL, but don't want to leave our RedGate tooling behind.

If I'm making changes to a new version of an application and I am working on 2 separate databases, I'd like to be able to only grab and compare changes that were done last week for instance. It will show me new changes made on the original application last week, but it won't show me ones that are different from a month ago because I already know about those.

A lot of CMS packages use SQL Compact Edition databases, and it would be really useful to be able to compare those.

Some text in popup windows is unreadable when using large font displays. Because these windows do not allow re-sizing, the user can not adjust the window size to see the text. There is no reason that all windows should not allow re-sizing.

Please make the columns (Type, Owner, Object Name) sizable

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'

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.

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.

It would be great to alert when column orders of tables don't match. These are important when doing bulk inserts inside applications.

script creator should be better aware of dependencies such that creating/altering a view or stored proc only occurs AFTER the underlying table has been updated to include the new dependencies. Currently the differences are scripted properly but just not always in order

Provide additional option to "use drop and create instead of alter" so that tables can be reconstructed blindly

i have found a problem - there are 5schemas showing up as needing creating in the syncronisation script, but the script produced has no dml to achieve this:

PRINT N'Creating schemata'
GO
IF EXISTS (SELECT * FROM #tmpErrors) ROLLBACK TRANSACTION
GO
IF @@TRANCOUNT>0 BEGIN
PRINT 'The database update succeeded'
COMMIT TRANSACTION
END
ELSE PRINT 'The database update failed'
GO
DROP TABLE #tmpErrors
GO

xml, html and excel reports for database differences (using options) include everything similarities as well as differences. Since, xml is excellent way to import data to SQL, it would be great if those reports included only differences (so that the file size is smaller). Right now the differences can only be output to text file if I am not mistaken.

I have a server that I have to change the password on a lot, and can never (rarely) remember if I have changed the compare tool for the new password. I guess I could switch the servers around so that was the first it tries to get objects from. BUT it would be a nice feature to have it fail before doing any actual work.

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.

I recently tried deploying a CLR assembly, with external access (yeah, yeah, move on), from a non-contained database into a contained database. SQL Compare's error message simply stated that it couldn't find the assembly upon attempting to create the dependent stored procedure. It would be helpful if SQL Compare could add to the error message that external access (and unsafe) CLRs are not supported in contained databases.