Keep Static Data Stored in PK Order
When storing the data items in files, it would be good to keep everything in PK order so that changes are easier to spot. Historical order is less important when working with static data.
Wolfgang Reh commented
I agree. This needs to be part of the software. How can you every use a *_Data.sql file with any kind of source control system when the order or the rows is not consistent. In the meantime I have to sort the data files manually which only works if the primary key is in the first column(s)
Redgate, you must be kidding! Please get your priorities straight on this one!
This is not a feature request. This is one solid bug that makes this product pretty much useless!
How can you possibly switch the order of records between left and right side and expect to get any kind of useful comparison result??
Just to make sure you really understand the implications of this: My coworker and I are working in a Shared DB setup and while my SQL Source Control reports the static data table as unchanged, her SQL Source Control does flag it as changed because hers is exporting the records for the exact same table in a different order than mine!
Please treat this as the critical bug that it really is and get it fixed!
I can not believe that you have been kicking this can down the road for 2 years now...
Ed Morris commented
PLEASE DO THIS NOW!!! Merges are a nightmare in the db mostly due to this non-sense of not ordering by key.
Tony Mudd commented
This feature would reduce the chances of conflict and make manually checking the changes much easier.
This would be tremendously useful feature to improve source code merge process.