Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
roma
Starting Member
1 Post |
 Posted - 2004-07-19 : 01:04:13
|
| Hi,i am a beginer with SQL server 2000.We have a win2K server small bussines edition.I try to run a merge replication. It looks OK, only one problem:replicaion create an extended identity column in the table of Distributer and Subscriber. This is gave an error on insert after the replication.How can I avoid creating this column?Pleace, be more detail.Thanks' |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-07-19 : 12:58:41
|
| What is the error?Tara |
 |
|
|
eyechart
Master Smack Fu Yak Hacker
3575 Posts |
Posted - 2004-07-19 : 13:56:43
|
| You can't avoid creating this column. Replication adds these columns in order to keep track of what has changed.I am guessing that your error is occuring becuase you are not naming the columns of the table you are inserting into.-ec |
|
|
|
ravilobo
Master Smack Fu Yak Hacker
1184 Posts |
Posted - 2004-07-20 : 05:38:42
|
quote:
Originally posted by roma
Hi,i am a beginer with SQL server 2000.We have a win2K server small bussines edition.I try to run a merge replication. It looks OK, only one problem:replicaion create an extended identity column in the table of Distributer and Subscriber. This is gave an error on insert after the replication.How can I avoid creating this column?Pleace, be more detail.Thanks'
I don't think it is an identity column. it should be a GUID column.While inserting records in the table exclude the GUID column...because that column has a default value of NEWID().------------------------I think, therefore I am |
|
|
|
|
|
|
need help with replication