November 19, 2009 at 3:52 am
Hello Everyone,
Yesterday, I have scheduled the snapshot agent for publication to run everyday at midnight. Then I realised that I dont need to run them everyday, I, have deleted the publication and created new one with option "Create a snapshot immediately and keep the snapshot available to initialise the subscriptions" . However job created shows on schedule (description) "Occurs on 18/11/2009 at 00:00:00" and I'm getting the error on my application log frequently stating "Cannot perform bulk copy on the table".
To investigate this further , I went and created another new publication with immediate snapshot creation and found that job properties shows on schedule (description) occurs on 19/11/2009 at 00:00:00).
Im assuming that SQL server has not removed my initial setting of running the job everday at midnight.
Only possible solution Im aware is to mark the end date on schedule the snapshot agent dialog .
Is there any other solution possible?
Ta
November 19, 2009 at 4:47 am
An Update...
As said above since there is an error delivering the snapshot , I have found that StoredProcdure/Job sp_msacquiresnapshotdeliverysession_lock seems to hold lock on publisher table which is bringing other application down.
Ta
November 20, 2009 at 7:47 am
An update.
Lock has been caused due to continous synchronization of large volume of data which generates the lock if we try to do future synchronization process immediately before it had transfered the data for first process. Now this issue has been resolved.
Ta
November 20, 2009 at 8:20 am
you could have tried with Sync_Method='concurrent' for SP_Addpublication stored procedure which will not lock the publicaiton table during snapshot
subban
November 20, 2009 at 8:36 am
Thank you. Will look in to that in detail.
ta
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply