dbcc checkdb

klomper2007

Our dba has been looking at performance on our SQL 2005 Enterprise server and noticed that every time before a set of polls the command "dbcc checkdb" is run.  I called support and they mentioned that is the way Orion was designed and it is to check if the database is available or not.

 Our dba is concerned this is overhead we don't need and would like our application to stop that.  Support didn't know a way of turning this off...does anyone know?

 Thanks.

FormerMember

Per Microsoft...

Best Practices

In SQL Server 2005, running DBCC CHECKDB with no options may take considerably longer than in earlier versions. This behavior occurs for the following reasons:

• The logical checks introduced are more comprehensive.
  
• Some of the underlying structures to be checked are more complex.
  
• Many new checks have been introduced to include the new features in SQL Server 2005.
  

Therefore, we recommend that you use the PHYSICAL_ONLY option for frequent use on production systems. Using PHYSICAL_ONLY can greatly shorten run-time for DBCC CHECKDB on large databases. We also recommend that you periodically run DBCC CHECKDB with no options. How frequently you should perform these runs depends on individual businesses and their production environments.

Can someone from SW comment on what implementation Orion uses, PHYSICAL_ONLY option versus no options?