RE: Ms SQL server db options for performance issues after db corruptio

From: Curt Spanburgh (CurtSpanburgh_at_discussions.microsoft.com)
Date: 09/07/04 

Date: Tue, 7 Sep 2004 13:17:17 -0700

Hi Nick. What is the application running on SQL?

"Nick Dakoronias" wrote:

> Hello SQL forum readers,
>
> I have a customer using Ms SQL Server 2000 SP3 installed on optical RAID-5
> Disk Array (IBM Fast200 SAN).
> After a disk failure his production db was corrupted and since the failed
> disk was replaced, cust. restored a valid backup
> in order to support his business operations (with one day transcations
> loss).
> We have dome a lot of troubleshooting and investigation (traces, logs,
> dumps) in order to identify what caused the corruption.
>
> But now, cust. faces low performance problems.
> I have already suggested to use additionally the following options :
> A) Auto Options:
> Auot create statistics
> Auto update statistics
> B) Recovery Options:
> Recursive Triggers
>
> I would be much appreciated If I could have any advise regararding any
> additional db option setting that could assist :
> a) What about Quoted Identifiers or other SQL option?
> b) What about Torn Page Detection (recovery option)
> c) Any other cursor options that could assist?
> Is there additional MEM/CPU overhead by enabling those options?
>
> I have also advised cust, to execute the command SET SHOWPLAN_ALL in order
> to gather details abour executed statements
> Anything else I can do?
>
> Any advise will be much appreciated.
> Thanks in Advance
>
> Regards, Nick Dakoronias
> IBM Athens/Greece
>
>
>
>
>

Relevant Pages
Loading