Options
Source Control Static Data File Order
richardhudson
Posts: 3 New member
Hi All,
Is there a way to set the order of the insert statements in the Data folder under source control to that of the tables primary key. Currently when changes are made, those changes are shown at the top of the file, making any view of data change history impossible through file comparison. We are mostly using source control for static data, and the ability to compare files rather than SQL would benefit us greatly when understanding the changes that our development team have made.
Thanks.
Richard
Is there a way to set the order of the insert statements in the Data folder under source control to that of the tables primary key. Currently when changes are made, those changes are shown at the top of the file, making any view of data change history impossible through file comparison. We are mostly using source control for static data, and the ability to compare files rather than SQL would benefit us greatly when understanding the changes that our development team have made.
Thanks.
Richard
Tagged:
Comments
I am afraid that this is not possible.
To compare source controlled static data and scripts folders you could use SQL Data Compare:
http://www.red-gate.com/products/sql-de ... a-compare/
https://documentation.red-gate.com/disp ... ta+sources
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
I am afraid to say, but this is not on the roadmap at the moment.
If you want you can suggest this as an enhancement in our uservoice forum:
https://redgate.uservoice.com/forums/39 ... ce-control
That forum is an important source that we consult when deciding what features to add or enhance in SQL Source Control.
Thank you,
Product Support Engineer
Redgate Software Ltd
Please see our Help Center for detailed guides on how to use our tools
We need the exact same thing, so if it's not there, I might raise it myself.
I like this idea. It's really more a Data Compare item, but I'll let them know.
The lack of this feature makes merge conflict resolution extremely difficult and error prone. The presence of a primary key is already enforced in order to source control the data in the first place and, since in most cases primary keys are also the clustering key, adding an order by should have minimal impact on performance when retrieving the data.
To circumvent the lack of this feature, we have resorted to manually ordering the data files before committing them.