all groups > sql server replication > september 2003 >
You're in the

sql server replication

group:

Transactional Replication - Identity Fields



Transactional Replication - Identity Fields Tom
9/4/2003 12:58:10 PM
sql server replication: Background:
1) SQL 2K SP 3 running on Win2K Servers
2) Original Snapshot Created via DTS Export from
Publisher to Subscriber
3) Subscriber is 'primed' via script for removal of
certain defaults, identity columns etc.

The problem.

I have certain tables that have Identity-Insert OFF on
both the subscriber and the Publisher for Replication.
This is appropriate for these tables. There are literally
thousands of inserts done every day that work perfectly.
Yet every now and then, I have an update on the subscriber
that somehow has the Identity field included in the
insert 'Fields' list. The insert works fine on the
publisher, so I know the Identity field wasn't used when
the original transaction ran.

How is this possible? I have financially crucial data
dependant on the keys and identities in these tables. Is
replication reliable or not? Or am I crazy?

Thanks,
Re: Transactional Replication - Identity Fields Hilary Cotter
9/5/2003 12:41:38 AM
replication is reliable - your users may not be:)

We have faced the same problems. The users on the subscriber swear up and
down they did not make changes on the subscriber, however when you catch
them red handed......
[quoted text, click to view]

Re: Transactional Replication - Identity Fields Tom
9/5/2003 4:34:24 AM
Hilary,

Thanks for the response. The situation here does not
allow users anywhere near the Subscriber. Their only
contact with the Publisher is via the front-end GUI. This
is VERY tightly controlled. That's why I'm so stumped.

Tom


[quoted text, click to view]
AddThis Social Bookmark Button