June 30, 2010 at 1:10 am
Hi All,
We have a bunch of databases hosted on SQL Server 2005.
Very randomly (once in 3 to 5 months) we have came across instances where on some day database started responding very slow. then after investigation we figure out that indexes were dropped. We are not able to figure out how, Why and on what basis they were dropped. The tables are also randomly chosen.
We tried to capture all DDL changes using a trigger but that trigger was eating up CPU, so we have to disable it.
Any ideas to figure out how we can catch this incident or to rectify this.
June 30, 2010 at 1:42 am
DDL trigger (filtered to drop index) or a server-side trace.
A well-written DDL trigger shouldn't have much if any impact. DDL should be a relatively infrequent operation (other than stats updates)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply