Viewing 15 posts - 61 through 75 (of 1,097 total)
First you should remove all the subscriptions to the publication (check sp_dropsubscription, sp_subscription_cleanup, sp_droppullsubscription), then you should drop the publications (with sp_droppublication) and then you can disable replication in the...
October 20, 2004 at 2:01 pm
Try to force the distribution agent to see if it is still working or if shows any error.
You can do this by running the Job of the distribution agent in...
October 20, 2004 at 7:49 am
be sure to check that the log reader agent is running. If you have transactions marked for replication and the log reader doesn't put them in the distribution database, then...
October 18, 2004 at 9:33 am
If you ment "lock", then you can deny access from EM.
October 15, 2004 at 12:17 pm
I have always added a column with that sp, after the snapshot was applied. Because sp_repladdcolumn add a column at the publisher and the subscriber when the distribution agent runs.
Try to...
October 15, 2004 at 11:31 am
No. Changing the recovery model doesn't affect replication.
October 15, 2004 at 10:09 am
I did it once. Can't give you all the step by step process.
Just remember that I build some .bat files, that prepare the dial process with RasDial command. Check the...
October 15, 2004 at 10:07 am
The trigger you losted, was at the publisher or subscriber?
October 15, 2004 at 9:14 am
Did you also restore the distribution database with the published database of the publisher?
Check the sync with backup option in BOL.
October 15, 2004 at 8:17 am
In the publisher, you must add the other server, as a valid subscriber. You can do this by right clicking in Replication/Configure Publishing, Subscribers... from EM, and adding the subscriber.
The...
October 15, 2004 at 8:13 am
By using sp_replAddColumn there is no need to regenerate the snapshot, also there is no need to pause the server as Microsoft suggest.
If you are using stored procedures to replicate transactions,...
October 15, 2004 at 8:10 am
Check if in the subscriber someone is making changes to the published tables, or also check for triggers that can be changing the replicated data.
Also you shoud check the stored...
October 15, 2004 at 8:05 am
Check that there isn't anothuer log reader running in the server. Maybe someone started from the command line.
Run sp_who2 to check the process and kill it, and then start the...
September 23, 2004 at 6:35 am
Still having the same problem. I have tried the last link you sent, but i have everything right.
The windows account I use to start sql services is member of the...
September 13, 2004 at 8:45 am
Mmm, I disagree.
The SQL Agent proxy account is a windows account in wich non sysadmin SQL users will use to access OS and network resources, by running xp_cmdshell or jobs.
All...
August 13, 2004 at 12:32 pm
Viewing 15 posts - 61 through 75 (of 1,097 total)