I am trying to solve this issue. Basically we had 1 database and we use the SQLMaint (Maintenance Plan) to do the Integrity Check and Optimisation and it's always failed for this particular database.
Looking the SQL Log ... and no error get recorded about this. Then looked at the Event Viewer and this error that I got for Optimisation which is there is nothing to say really.
quote:SQL Server Scheduled Job 'XXX_SERV_PROD: Maintenance Plan - Optimizations Job' (0x2F273B248B1A0B45A90E4FD9E5BB57DC) - Status: Failed - Invoked on: 2006-10-08 01:00:02 - Message: The job failed. The Job was invoked by Schedule 26 (Schedule 1). The last step to run was step 1 (Step 1).
Any ideas what might be causing it? We are using SP3a and we have about 60 databases for prod and uat and dev and we don't have any issues regarding except this database.
Check DBCC CHECDB regularly for this database and return no error.
quote:CHECKDB found 0 allocation errors and 0 consistency errors in database
The database doesn't set as a fixed size.
I might try do Reports to Generate option.
When you said: "Otherwise you need to preform the reorganisation steps manually and see what fails.", do you mean manually using DBCC CHECKDN stuff? Does anyone know the equivalent SQL Script for Integrity Checks and Optimasation.
quote:Check the current setting of SET QUOTED_IDENTIFIER option by using DBCC USEROPTIONS and make changes accordingly.
I did run the DBCC USEROPTIONS and the value sets as SET which I belive is ON.
My question is: Is the SET QUOTED_IDENTIFIER isolated only for the database level or it's actually entire server configuration? If it's a server configuration which will be affecting entire database ... I rather not going to apply this.
quote:Do you have a table with a computed column in the database where you have this problem?
No I don't have that table with a computed column. There are hunders table in this database and it's going to be pain to search this.
So my question is: Is the SET QUOTED_IDENTIFIER isolated only for the database level or it's actually entire server configuration? If it's a server configuration which will be affecting entire database ... I rather not going to apply this.
I think it is specific to the database rather than to the server.
What i have done in the past is to go into the maintainance plan in question and write a set option for the quoted_identifier and then place a go statement just between the set lption and the maintainance plan script
quote:What i have done in the past is to go into the maintainance plan in question and write a set option for the quoted_identifier and then place a go statement just between the set lption and the maintainance plan script
I did try this by doing this:
quote:SET QUOTED_IDENTIFIER OFF GO
EXECUTE master.dbo.xp_sqlmaint N'-PlanID 02D8A981-13DF-471D-8513-45A0C27BBF23 -Rpt "D:\Program Files\Microsoft SQL Server\MSSQL\LOG\XXX_SERV_UAT DB Maintenance Plan2.txt" -DelTxtRpt 4WEEKS -WriteHistory -CkDB ' GO
and it's the same error. What really bothering me is if I run DBCC CHECKDB('XXX_SERV_UAT') and no error what so ever ?!?!