hey all,
I was setting up a replication job on a server. I was setting up the publisher end. I used the wizard to create a scheduled job to do a snapshot of one of our databases.
I completed the wizard and clicked Finish. The progress window appeared and it appeared to get hung on step one of the process (Adding articles). I killed the job via Task Manager. This was at 2:11 pm.
At about 3:30 pm, the server started to become very slow. I brought up Performance Monitor and the Pages/sec was maxed out. CPU usage was at 11%. Memory consumption was at about 50% of total memory.
The issue did not clear up and we had to bring the server down and restart it to clear up the issue. This was at 4:00pm.
Looking at the error logs, there is a warning for stopping the replication publisher job and removing it. Then there is an error message regarding a "deactivated schedule 41". Then errors from bringing the server down.
I'm wondering if it is possible for the replication publisher job that I killed to have kept running in the background gobbling up resources. I've done a search of the internet and several forums and I've found nothing conclusive.
screen shot of the error logs but I can't insert it yet until my account is verified.