when i run the bcp in DOS window it loads the data but gives the following error, i think this might be my issue. but how to interpret this error?...

The table is identicle , I am not using identity columns, and this table replicates perfectly on other subscribers which tells me that it must have something to do with...

but how do i now find out the dates that are older than 10 mins ? dont i have to use datediff ?

yes i have int form numbers as date like follows :

1346447979

1346447493

here is what sp_helpserver shows :

I dont know what is SUNPASS2 ...never added this server name

DOTSTOSUNPASSDB\SUNPASSDB1DOTSTOSUNPASSDB\SUNPASSDB1 rpc,rpc out,use remote collation0 NULL

repl_distributorDOTSTOSUNPASSDB\SUNPASSDB1 rpc,rpc out,system,use remote collation2 ...

and let me put the question in this way : If I have SP4 applied how can I see if KB960083 patch has been applied or not ?

hi Bob !

you said 'I dont have service pack4' but I do have SP4 , if I check the database properties it says SP4 ?

if SP4 is seperate from security patches how do I know if that security patch is applied to the database or not ? this puts me back to squre one...

thanks that link was very usefull , just the right info I needed

so is this security path including in SP4 and I dont need to worry about it ?

Security Update for SQL Server 2000 Service Pack 4 and MSDE 2000 (KB960083)

Microsoft SQL Server 2000 - 8.00.2050 (Intel X86) Mar 7 2008 21:29:56 Copyright (c) 1988-2003 Microsoft Corporation Enterprise Edition on Windows NT 5.2...

no iam looking for the 32 bit equivalent for the following :

http://www.microsoft.com/downloads/details.aspx?familyid=8316BC5E-8C2D-4710-8ACC-B815CCC81CD4&displaylang=en

SQL2000-KB948111-v8.00.2273-x86x64-ENU.exe

as you can see this security update is for 64 bit, I need 32 bit.

I had to do the same thing last thing and I updated the msdb.sysjobs table to point to the new instance name , I didnt modify sysservers table...

i forgot to mention , its 32 bit machine .

found the problem. . its a microsoft bug for sqlserver 2000 . ..

and there is a work around

http://support.microsoft.com/kb/827448