March 23, 2009 at 5:28 pm
Hi,
I had an issue with the integrity check portion of my maintenance plan where it would just fail. However if I ran a checkdb manually on each database it was successful.
I looked in the SQL properties and noticed another DBA (and I use the term losely) had unticked the automatically set processor and I/O affinity and just ticked the CPU1 option. I changed it back to be automatically and now my maintenance plans work.
Can someone please explain to me why?
Kris
March 23, 2009 at 10:34 pm
My understanding of that is if you check that setting to only one CPU you are telling SQL Server to not do any parallel activity. And if you are going to do that why have a multi-core CPU? You might need to do this if you are running multiple instances on a server and you want to grantee that one instance gets CPU also (although I have not run into issue where SQL can't manage that).
As to why your job started failing, I would think the CPU was being taxed too much? Blocking? Timeout issues?
If you can paste the error you were getting that might provides some more hints...
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
March 23, 2009 at 11:00 pm
Thanks for that I think you might be right. That's the problem is there are no error message of any use. Just "Alter failed for Server 'Servername'" and in the job logs it just says "the step failed". I found a blog that said to set those parameters and it worked I just didn't know why.
Thanks for your help
Kris
March 23, 2009 at 11:06 pm
I recommend you start logging to a log file; SQL Server records far more details there then it records in in the Maintenance Plan logs or the SQL Server Job Logs ...
Thanks.
Mohit K. Gupta, MCITP: Database Administrator (2005), My Blog, Twitter: @SQLCAN[/url].
Microsoft FTE - SQL Server PFE
* Some time its the search that counts, not the finding...
* I didn't think so, but if I was wrong, I was wrong. I'd rather do something, and make a mistake than be frightened and be doing nothing. :smooooth:[/font]
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply