March 15, 2010 at 11:46 am
So all of a sudden on my server, any job that does an update stats is failing. This started last week. The error involves ARITHABORT so suggests a computed column causing the problem. So using MS recommendation I have pasted
SET QUOTED_IDENTIFIER ON
SET ANSI_NULLS ON
SET ANSI_PADDING ON
SET ANSI_WARNINGS ON
SET CONCAT_NULL_YIELDS_NULL ON
SET NUMERIC_ROUNDABORT OFF
SET ARITHABORT ON
at the start of any sql maintenance jobs involving indexes.
But the big problem for me is that one of our important overnight tasks, that populates a mass reporting solution, is failing due to the same issue (I say that - it errors and doesn't run step 2, but it doesn't rollback or fail at the point the issue occurs...its just a warning perhaps?)
Anyway I queried syscolumns (2000 box to be honest) where iscomputed = 1 and found a column that this stored proc populates that is a computed column. No index against the column but it does have auto stats applied. I am on the side of the fence that this may be causing the issue, but I cannot understand why it suddenly occured last week.
So I am a bit torn how to fix, as sticking the solution for maintenance tasks in at the start of this stored proc could cause problems with other areas of it. If it is auto stats against a computed column, would it be the attempting update of those stats causing the issue?
Any suggestions?
Shark :hehe:
March 17, 2010 at 6:54 am
I resolved this. Sadly I did 2 fixes on the same night so not sure which fixed it.
Firstly, I added the db settings mentioned previously before the update stats job runs. But I also manually removed the autostats generated on the computed column. I am not totally sure, but assume the server will recreate these at some stage!
Shark
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply