Viewing 15 posts - 1 through 15 (of 94 total)
Using the Replication Monitor gui should allow you to do this. Locate the relevant Log Reader Agent, highlight it, right click and choose properties. You can then set a schedule...
December 15, 2009 at 2:55 am
An explanation of what you are trying to achieve would help as would the DDL. It looks like the error is in this:
'TransferCluster'',' 'TransferConsolidate'
These are two separate strings, given...
December 15, 2009 at 2:03 am
A number of ways of doing this:
SELECTCONVERT(datetime,CONVERT(char(8),MyDateTimeColumn,112))
FROM MyTable
or
SELECTCONVERT(datetime,DATEDIFF(DD,0,MyDateTimeColumn))
FROM MyTable
Hope that helps.
Mike
December 2, 2009 at 1:57 am
Given you posted this a week ago you may have found the answer. In case you haven't then you can use sp_browsereplcmds which is run in the distribution database. It...
November 27, 2009 at 3:19 am
At this point in time, all I can suggest is dropping replication, making your changes, putting replication back on once you are happy that all is well and then generating...
November 5, 2009 at 10:05 am
I'm assuming these are data changes not schema changes. I'm also assuming these changes can't be tested in an environment where they can be checked before going into production. Since...
November 5, 2009 at 8:30 am
I suppose it depends on where you are happy to have a backlog build up. You can disable and stop the Log Reader Agent job in which case the log...
November 5, 2009 at 7:17 am
On the distribution server, get the value of srvid from master..sysservers which corresponds to the publisher. Next, get the article id from the msarticles table in the distribution database. Then...
October 21, 2009 at 1:50 am
Sounds like you have a fundamental problem somewhere because you shouldn't be timing out. In the odd bad moment I've had distribution databases with a backlog of 100GB and never...
October 9, 2009 at 9:46 am
Given our experience, I would say stick with the continuous running. Running on a schedule will build up latency and the distribution agents can slow down as the distribution database...
October 9, 2009 at 2:58 am
The first thing to is to change the schedule of the Distribution Cleanup job. By default it runs every 10 minutes which will kill a busy replication system. We run...
October 9, 2009 at 2:10 am
Ah, well spotted. I've seen all those appear but have never really read them too closely. That'll teach me!
Mike
September 14, 2009 at 2:16 am
Sorry for not replying sooner. Glad you've got it working.
Mike
September 10, 2009 at 3:22 pm
Sorry for not replying sooner. I don't appear to have received a notification indicating that you had replied to my post. Mind you, knowing me I probably accidentally deleted it.
I...
September 9, 2009 at 4:55 am
Viewing 15 posts - 1 through 15 (of 94 total)