Duplicate inserts creating an error

Strange issue (aren't they all). On my VB.Net app, I use merge replication.
Everything appears correct with synchronization and data flows in both
directions. However, I have noticed that on the SQLCE tables where I do
multiple Inserts, I'm now getting an error after the second synchronization.
For example, I do a download of the data, do Inserts on some of the tables,
then merge upload the data to the server. Now I go back for a second
download, and when I try to do an Insert, I get the error, "A duplicate
value cannot be inserted into a unique index".
I'm not trying to insert a primary key or into a primary key field, and I've
deleted all the indexes on any other fields -- except the uniqueID fields
created by the publication creation.
Not sure where I'm going astray here, so any advice would be appreciated.
Which table are you getting this error on? Is it a system table or a user
table?
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
|||User tables on the PocketPC.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:opsoxx6ntqrj9kur@.hcottter-lap.ap.org...
> Which table are you getting this error on? Is it a system table or a user
> table?
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com

Dump Huge

A dump of our database is growing more huge by the week, but we aren't doing
much with it. Properties show it us about 13gb in size, but the dump three
weeks ago was 26gb, and today it is 41gb. I dumped tran with no_log and ran
shrink, but that didn't seem to do anything. What's up with this?
Jay Marvin (JayMarvin@.discussions.microsoft.com) writes:
> A dump of our database is growing more huge by the week, but we aren't
> doing much with it. Properties show it us about 13gb in size, but the
> dump three weeks ago was 26gb, and today it is 41gb. I dumped tran with
> no_log and ran shrink, but that didn't seem to do anything. What's up
> with this?
How does your BACKUP command look like? It sounds like you are backing up
the database to the same file each time, but you are not using WITH INIT.
In that case the backup is appended to the file.
You can examine this with RESTORE HEADERONLY on the backup file. If you
get more than one row back, there are multiple backups in the file.
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx