Replication Server and TIMESTAMP datatype

[JenJohnson]

Just found out from my DBAs that timestamp is an unsupported datatype when it comes to replication server. This datatype is part of the primary key of a table that needs to be replicated. We've discussed changing the datatype of the field from timestamp to datetime, but found that datetime was accurate only to the millisecond and there is a possibility of more than one record being inserted to the table in less than a millisecond, so, records could not be reliably sorted.

Has anyone else dealt with something like this, and feel up to sharing their thoughts or solution?

Many thanks!

 

[hmo]

hi,

in the primary database you can use a timestamp datatype, but in the replicate database ,you must use the varbinary(8) datatype instead of timestamp

regards

 

[JenJohnson]

FINALLY, after much debate with the DBAs, we've implemented a sorta different method of replicating the table in question. We replicated all columns except the timestamp column, and let that self-populate in the secondary table. The column is not part of the key, so this wasn't an issue for us.

Thanks for your input!