Viewing 10 posts - 1 through 10 (of 10 total)
I thought I'd bump this question because I'm still struggling with the problem. Does anyone have any thoughts?
February 28, 2012 at 10:15 am
savethytrees (2/14/2012)
Try to run the snapshot agent job instead of using the replication monitor or any other tool in SSMS.
It gives the same result. Already tried that.
February 14, 2012 at 10:57 am
Roy Ernest (2/10/2012)
Just a shot in the dark, Did you try running the SSMS in administrator mode. Right click on SSMS and use the Run as adminstrator option.
Unfortunately, that didn't...
February 10, 2012 at 7:01 pm
Hi again guys
Sorry that I haven't replied here for a long time, but I still haven't got time for optimizing the SP. My boss won't allow ressources for that task...
February 24, 2009 at 12:44 am
Thanks for all the good comments. They are much appreciated!
I will look into optimizing the SP in this week, when I have reported all the statistics to our sales department....
January 19, 2009 at 7:38 am
I do not know much about large stored procedures and performance, and I did not develop the whole procedure. I have made some changes and thats it.
I am really looking...
January 16, 2009 at 10:23 am
Haha guys 🙂
I had lots of other work that I could do while the job was running, so it was no problem really. But when the running time got over...
January 14, 2009 at 1:52 am
Thanks for all the answers. Luckily, the SP finished last sunday so I don't have the problem anymore. It only ran for ~470 hours 🙂
January 13, 2009 at 6:51 am
Hi Jeff
Yea - 17 days and you're correct, it is for a year report and I don't have time to stop it and then run it again 🙂
How do I...
January 9, 2009 at 8:42 am
That makes sense.
Guess I have to run the SP again. Too bad 🙂
Thanks for you answer.
January 9, 2009 at 12:46 am
Viewing 10 posts - 1 through 10 (of 10 total)