February 7, 2006 at 8:23 am
I setup a transactional recplication and selected the 'Do not lock tables during snapshot generation' option so to allow the publication DB to be available while snapshot is being generated. Snapshot completed OK but the distributor returned error:
Operand type clash: uniqueidentifier is incompatible with int
(Source: SQLCLUSTER02\SECONDARY (Data source); Error number: 206)
However, If I unselect the 'Do not lock tables during snapshot generation', the distributor replicated the DB without error.
Any have experience similiar problem. Thanks in advance for your help.
JC
February 7, 2006 at 2:59 pm
Wich version and Service pack do you have in publisher, distributor and subscribers?
February 8, 2006 at 4:01 am
This sounds like a bug. Can you tell me your sql server version (@@Version) and post your publication script, and table schema (with indexes) here?
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
February 8, 2006 at 7:49 am
We are on 'Microsoft SQL Server 2000 - 8.00.2040.' (i.e SP4). I was not allow to post company scripts and schema without approval. We are using transactional replication without filtering and the replicating articles all have the msrepl_tran_version column define as teh last column.
Does anyone use this option? and does it work? Checking this option, SQLServer forces a complete re-initializing of all subscribers (It ask for comfirmation first). So , execrise caution when usingt his option.
Another question, while snapshot is generating will it lock one table at a time or will it lock all tables until it finishes? I don't have consistent answer when check with different sources.
Thanks for your quick reply and support !!
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply