I've just had this probem and it turned out that the table that it was erroring on had a diffrent definiton on the subscriber compared to that on the publisher....

You would think that they would do the samething, however without a reindex the defrag time will continue to creep up, and so although it would be nice just to...

The DBReindex takes about 3-4 hours and we've now started to run it once a week as this allows us to keep the defrag & check table time down to...

The only time we had this error was when the mechnasim that keeps the times on all the servers in sync went crazy and because the time on the domain...

Personally I don't it matters what job you are applying for...Suited and booted always!!!

OK, problem solved. Because I had changed whom the report server service ran as, it had no symmetric key info for this new user.

I had something similar and was cuased by an incorrect password in the datasoure(we were using stored credentials). Who are you connecting to the DB as?

It's best to use credentials of a domain user expecailly if the file share is on another machine. in the form <domain>\<username>.

Hope this helps.

An update on this managed to get it working by running the report server service as localsystem instead of a domain account, however this now breaks email subscriptions. Any ideas??

Jeet

Also have alook at this thread...

http://www.sqlservercentral.com/forums/shwmessage.aspx?forumid=65&messageid=269738#bm272159

As stated above you can drop the fk's and then recreate them. Or an alternative is to disable them do the import and then re-enable them.

DISABLE WITH

alter

...

So is the insert failing because the trigger is failing?

What is the error? It might be a permission issue?

Deadlocks usually mean that other processes outside of your package are trying to access the same resouces (tables) as your stored proc. If your sproc is running for three hours...

I plan to do it in live soon, however in our test system we did the dereindex first and this dropped the nightly DBCCS by 20%, the defrag made no visible...

if you drop the table name prefix in the where so it looks like...

DELETE FROM @tbl

WHERE ID = (SELECT dbo.PersonList_Person.PersonID FROM dbo.PersonList_Person WHERE dbo.PersonList_Person.Include = 0)

or

DELETE @tbl FROM...