you have to re-initialize replication with no synch or drop te SUB & run the snapshot.

thanks for your reply. but i need to get data out first from TXT file before i try to put into Staging table.

Second thought about DTS & Service Broker.

First of all thanks every body your feedback & i appreciate that. i am going to get pipe delimiter txt file with most of dupllicate rows with same customer name....

Thanks for your all help & reply & especially for the script that you gave was helpfull & thanks to mention System tables name.

Sorry, forgot to mention about "sp_browsereplcmds" run this where your Distribution Database is & that will give you some more info.

There are other ways that this problem can be FIXED. But depends upon size of Database. i did following 2 steps.

1>Re-intialize

2> Apply Snapshot.

that fixed my PK error.

i hope this help.

NO, you have to re-intialize PUBLICATION.

Perhaps the most frequently used procedure is sp_browsereplcmds. but below are some more that will help you. I got this info from sqlservercentral.com. you can also add -skiperrors...

If security is in question then you can put SQL Servers in DMZ & open certain ports at firwall.

For the first question:- when ever SQL Server is started it goes into recovery. if you open the SQL log file you will see in detail information what it is...

you may have to create step in your SQL Agent JOB or point to the SP that will be defined in that STEP.for e.g. STEP 3 which will execute STORE...

did you check the user(Window/SQL) created on the server & default Database while creating.

This article doesn't make any sense. professionalism still exists & still company out there is looking for experienced & professional IT canidate. people likes sober & mannered person in there...

Also you can think about Database mirroring if that option is open.