Handling Surrogate key

naren6876 · Post by **naren6876** » Thu May 14, 2009 2:40 pm

Hi,

I have a requirement like .......

The target table is updated by multiple sources concurrently how do I make sure that they will have unique surrogate keys?

Any info would be appreciated.

Thanks in advance.

chulett · Post by **chulett** » Thu May 14, 2009 2:59 pm

By making sure they all "buy them at the same store" - be that a sequence object or by using the same sdk KeyMgt routine key value or whatnot.

Pull them from the same source and be prepared to handle concurrency - database sequences do that automatically and there is a 'Concurrent' version of the server routine that is available.

ray.wurlod · Post by **ray.wurlod** » Thu May 14, 2009 5:06 pm

*Topic Relocated - Content Editor*