I am running SQL Server 2005 x64 on Windows 2003 active/passive cluster. We
are currently having latency issues with our SAN, this is causing the SQL
Server instance to restart when the latency is high. We are addressing the
SAN latency issues with the SAN vendor but in the short-term I would like to
know;
1) What are the time-out settings for SQL Server for SAN storage?
2) Can these settings be modified and if so what other impacts may this have?

You can adjust the LooksAlive and IsAlive timeout settings inside the
Cluster admin tool. You cannot adjust the SQL disk timeout settings.

This is typically caused by having too many LUNs on a set of disks. Each
LUN has its own command queue but they get aggregated together since there
is a common set of disks. The total command queue depth exceeds the ability
of the SAN to service that queue.

Best practice for file shares = worst practice for SQL Database.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




"Jim Clark" <JimClark (AT) discussions (DOT) microsoft.com> wrote

94EB79AE15E3 (AT) microsoft (DOT) com...

We are having the same issue on this and are on the same version. How do you set the IsAlive KeepAlive values inthe cluadmin for these values or see what the values are.



Geoff N. Hiten wrote:

You can adjust the LooksAlive and IsAlive timeout settings inside theCluster
04-Oct-09

You can adjust the LooksAlive and IsAlive timeout settings inside the
Cluster admin tool. You cannot adjust the SQL disk timeout settings.

This is typically caused by having too many LUNs on a set of disks. Each
LUN has its own command queue but they get aggregated together since there
is a common set of disks. The total command queue depth exceeds the ability
of the SAN to service that queue.

Best practice for file shares = worst practice for SQL Database.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




94EB79AE15E3 (AT) microsoft (DOT) com...

Previous Posts In This Thread:

On Friday, October 02, 2009 2:01 PM
Jim Clark wrote:

SQL Server SAN timeout settings
I am running SQL Server 2005 x64 on Windows 2003 active/passive cluster. We
are currently having latency issues with our SAN, this is causing the SQL
Server instance to restart when the latency is high. We are addressing the
SAN latency issues with the SAN vendor but in the short-term I would like to
know;
1) What are the time-out settings for SQL Server for SAN storage?
2) Can these settings be modified and if so what other impacts may this have?

On Sunday, October 04, 2009 10:20 AM
Geoff N. Hiten wrote:

You can adjust the LooksAlive and IsAlive timeout settings inside theCluster
You can adjust the LooksAlive and IsAlive timeout settings inside the
Cluster admin tool. You cannot adjust the SQL disk timeout settings.

This is typically caused by having too many LUNs on a set of disks. Each
LUN has its own command queue but they get aggregated together since there
is a common set of disks. The total command queue depth exceeds the ability
of the SAN to service that queue.

Best practice for file shares = worst practice for SQL Database.

--
Geoff N. Hiten
Principal SQL Infrastructure Consultant
Microsoft SQL Server MVP




94EB79AE15E3 (AT) microsoft (DOT) com...


Submitted via EggHeadCafe - Software Developer Portal of Choice
Measuring SharePoint Page Rendering
http://www.eggheadcafe.com/tutorials...oint-page.aspx