Prev: SQL Agent terminates, then replication can't restart.
Next: cleanup msmerge_genhistory
From: Earl on 11 Jul 2007 12:10
Been awhile since I setup merge replication and saw an issue I recognized
but momentarily forget what the resolution was. Then I recalled the
solution. But I wonder why Microsoft would create such an obscure
NON-default setting.

I set up a publication on SQL2k. The rowguid columns were added by the pub
wizard. No problem with the replication to the mobile device, but when I try
to do an insert to a table on SQL2k, I now get the infamous message: "Cannot
insert the value NULL into column 'PocketPC_rowguid', table
'Prospects.dbo.PocketPCs'; column does not allow nulls. INSERT fails. The
statement has been terminated."

Hmmmm .. ok, now I vaguely remember this totally obscure but quite
significant issue. The solution is to add (newid()) as Default Value to the
rowguid column. But this should be the default anyway. Anyone know why this
was left out other than to do nothing more than totally befuddle the issue
of setting up replication?


 | 
Pages: 1
Prev: SQL Agent terminates, then replication can't restart.
Next: cleanup msmerge_genhistory