I do not want to source control certain columns in my reference tables (e.g., update date/times since these are different on each server and get set by a DEFAULT).

I can undo any DDL operation but I don't have the option to undo a data change in a source controlled table. I think data changes should also be in the list of changes I can undo.

I would like the ability to source control a subset of a table (perhaps using a view).

I have inherited a database where lookup data is intermixed with user defined data. We reference the lookup data in the table using a code (VARCHAR) that is unique when another field is NULL, so it is possible to ensure that records are created/updated/deleted without concern for the primary key involved.

For more information, you can refer to this forum post:
http://www.red-gate.com/messageboard/viewtopic.php?p=50087

Currently, SQL Data files contain a bunch of insert statements, but the order of the insert statements can be inconsistent. For example, new records might get inserted on the top or the bottom. Also, multiple SET IDENTITY_INSERT statements sometimes get created. This makes it difficuly to merge data changes between multiple branches in TFS Source Control. If the Insert statements had a consistent order and only included one SET IDENTITY_INSERT diffs and merges would be easier.

We have the same issue as noted here: http://www.red-gate.com/messageboard/viewtopic.php?t=13662&highlight=foriegn+foreign+key

The FK is recreated with NOCHECK during data sync which triggers a schema change.

It's only possible to check in entire tables when there is some data changes in them. I would like it to possible to check in/commit only selected rows instead of entire table.

We are a couple of developers that are using the database and while we are developing our different tasks we update our test database. When each task has a go to release we want it to be able to just check in that tasks specific alterations.

Our static data tables can have a few thousand rows each. It's costly to have the rows compared every time the SQL Source Control tab is opened to push/pull schema changes (which are much faster to compute). Can the schema and data aspects of this tool be separated to prevent excessive comparisons on data that by nature changes very infrequently.

I have my database linked to source control, and if I make a change to a schema, it shows a blue dot in the Object Explorer to indicate there are pending changes. However the same does not apply to static data – if I change some data in a table that is setup for static data source control, there is no icon to indicate there are changes to be committed. The data change does appear when I go to the commit changes tab however.

Do not use transactions but use bulk insert in order to reduce the get latest time. A 'flush and refill' approach using bulk insert should be faster in hours with 10K plus records.

A two processor, dual core computer with 8GB of RAM and a Windows experience index of 6.5 takes over 8 hours to get lates on 50K records.

We use Linked-Servers to connect to Oracle databases. These objects can be added by a developer and then need to be versioned like any other SQL object.

Currently when you try and publish static data, it only supports comparing the data in the source database, there is no option to use source control. Can it compare directly with source control and be limited to only the tables that are configured for static data?

I am trying to pick my tables for the static data feature I just dound and i'm using "explore data" to find the table I want to store the data for. The popup however is modal so I cant scroll the data explorer without saving the ones I just ticked.

Whe you have a multi branched dababase environment could be helpful to export from the main database the list of tables linked (in xml ie, or json, as you wish), in order to reload it on the branch database. Obviously only for the objects that exist. An alternative could be to save to "other similar database" too..

don't have to perform a count, just a quick look at sysindexes would be sufficient.

When we hop back in our source control repository to an older release and "update" our database, occasionally there is new static data that is referenced by non-static entries in the database. We do not have cascading deletes enabled for various reasons outside of the developers control, but in this particular instance it causes errors when static data is removed from the database to revert to an older version. Would it be possible to have redgate check incoming foreign keys and generate all the necessary deletes to allow static data removal?

I just did a data edit (inserted one row) but in the differences I see three rows inserted and two removed. Two of the rows inserted are letter for letter identical to the two rows removed.

Doesn't really matter, just a little confusing to read

When updating static data in source controlled table i need to disconnect and reconnect registered server in object explorer before Commit Changes screen picks up change.

Also seems to affect other changes