Viewing 7 posts - 1 through 7 (of 7 total)
Testing my complete update script and while its working, I now noticed through the profiller that for one table where as before it fetched 100 rows at at time from...
June 17, 2005 at 11:16 am
I found this post and low and behold it worked. http://dbforums.com/t507548.html. SET NOCOUNT was set on at server level on both servers. I turned this off at server level re-ran...
June 17, 2005 at 11:06 am
Are version is MDAC 2.80.1022.0.
No idea whats causing this error. I am stumpted.
June 17, 2005 at 3:45 am
I give up. I think I will go back to the old way of comparing the updatedDate field on the central DB with the remote DB and update where they...
June 16, 2005 at 10:08 am
Yes. I moved this script to a test SP as follows
CREATE PROCEDURE tester
(
@LastRunDate DateTime
)
AS
SET XACT_ABORT ON
begin distributed transaction
update ProductionDB.......
Commit etc....
I search the web but found nothing.
June 16, 2005 at 9:39 am
I have modified my sp and now i pass in @lastRunDate as a parameter and it works fine. As in the sp now runs in 3 sec where no updates...
June 16, 2005 at 9:25 am
I agree and thats the way I will be implementing it. However it would mean that if 5 rows in the master copy changed then all remote rows are copied...
June 16, 2005 at 7:38 am
Viewing 7 posts - 1 through 7 (of 7 total)