Just completed exporting our existing database to a liquibase changeset! Great tool!
However, after generating the changelog I used SQL Delta to compare the new database generated by liquibase with our existing pristine database and discovered a number of limitations with generateChagneLog which made the conversion a bit time consuming. I thought I would share what I found so that they can be addressed in future releases. Our current database is MS SQL 2005.
1) length of nvarchar columns are lost
2) nvarchar(max)/varchar(max) is converted to ntext/text
3) missing the ability to set the identity seed value on for auto increment column
4) missing option to make primary key non-clustered
5) missing ability to create defaults, on those columns where defaults were used it would generate the create default statement in default value which doesn't work
6) missing ability to include non-key columns on create index (http://msdn.microsoft.com/en-us/library/ms190806.aspx)
7) missing create statistics
8) missing column documentation (sp_addextendedproperty)
9) several indexes were not generated, but many were. I think most of them were those with non-key columns but some of those that were generated had non-key columns and I had to replace the create index with raw sql so I'm not sure why some were generated and others not.
10) several foreign keys constraints were not generated, but many were, not really sure why. I found a few tables in pristine database defined same foreign key constraint with different names and might have something to do with it, but these should still import so we can use liquibase to drop it.
11) missing check constraints
Is there any progress on any of these? Should they not be created as separate feature requests?
We are using the <sql/> tag a lot because of these issues, would be great to see progress
I've been doing a lot around improving diff support in general, but I won't have time to fully investigate this issue in 3.0