Activity overview
Latest activity by mako0201
bpage wrote:
[*]SQL Data Compare can reseed on an identity column too low. Say for example you have Server1 with a seed of 100 and Server2 with a seed of 200. Maybe this is a development server and there has been a lot of testing. When you synchronize from Server1 to Server2, Server 2's seed will a be set to 100 and the rows from 101 to 200 will be removed. However, if someone were to perform an Inserting during the synchronization there could be a row with a value of 201 in the identity column. This could by adding an option to let SQL Server recalculate the seed column.
DBCC CHECKIDENT('schema.table', RESEED)
I have the same issue! I'm running data synchronization on a table from server A to B with "include identity columns" option checked. The new seed value in the DBCC CHECKIDENT statement is getting set to maximum value in the identity column of the table but on server A!!! I think it should take maximum value in the identity column from the table on server B, as it is the server where the changes will appear, but maybe I'm missing something. Please advise. / comments
bpage wrote:
[*]SQL Data Compare can reseed on an identity column too low. Say for example you have Server1 with a seed of 100 and Server2 with a seed of 200. Maybe this is a development server a...