Posted by dhek on 11/04/07 14:11

>> The thing is I have a database containing various types of information -
>> for instance orders.
>> Instead of letting each record in an order contain a timestamp indicating
>> the datatime the record was replicated to another system, I have a table
>> containing replication times for various types of objects.
>
>
> Why not add such a column with a timestamp then?

Yes, I'd love to - but its not just up to me, since I don't have ownership
of the database.



>> This means that while I initiate a transaction selecting all new orders
>> it is possible for others to add other new orders to the database which I
>> will never be aware of.
>> - in my transaction after having gotten new orders I set a timestamp
>> indicating the datetime of my last replication. If someone has added new
>> records meanwhile I executed my select statement and performed the update
>> statement, then these new records will never be replicated because their
>> timestamp will be less than than the one I set in my update-statement
>> when finished.
>
> If you're simply looking to do replication, use SQL Server's built in
> replication functionality.
>
> It may save you a lot of effort.

Well, I'm not sure what the possibilities are really with regards to
replication from SQL server. I doubt that it is usefull in my case, since I
pull data from an SAP system.

[Back to original message]