Got my SQLIO Results... Now what?

I posted a similar message to SQL Tools group, apologize for the
double-post, but this is urgent...
I ran SQLIO against my SAN and got back some encouraging results. It
basically seemns to point to optimal performance settings of 64KB I/O's,
4096KB "stripes", with the Buffering option to "All". How can I make sure
Windows, SQL, et al. are using the same options that SQLIO used? Is there
something that needs to be set in the registry to ensure 64KB I/O's/4096KB
"stripes"/Buffering=All, or somewhere else in Windows (2003 Server), or do I
need to modify settings in SQL (2000), or what?
Thanks
In SQL 2000 you do not have to set any knobs.
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael C#" <xyz@.yomomma.com> wrote in message
news:%239MLdDNKFHA.904@.tk2msftngp13.phx.gbl...
>I posted a similar message to SQL Tools group, apologize for the
>double-post, but this is urgent...
> I ran SQLIO against my SAN and got back some encouraging results. It
> basically seemns to point to optimal performance settings of 64KB I/O's,
> 4096KB "stripes", with the Buffering option to "All". How can I make sure
> Windows, SQL, et al. are using the same options that SQLIO used? Is there
> something that needs to be set in the registry to ensure 64KB I/O's/4096KB
> "stripes"/Buffering=All, or somewhere else in Windows (2003 Server), or do
> I need to modify settings in SQL (2000), or what?
> Thanks
>
|||That's good to know. Now I need to know I *can* do with the SQLIO results.
So far the only use I've found is to print out hard copies so I'll always
have something handy to wrap raw fish with.
"wei xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
news:eteDqvTKFHA.3336@.TK2MSFTNGP09.phx.gbl...
> In SQL 2000 you do not have to set any knobs.
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://blogs.msdn.com/weix
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Michael C#" <xyz@.yomomma.com> wrote in message
> news:%239MLdDNKFHA.904@.tk2msftngp13.phx.gbl...
>
|||SQLIO results can be useful if you experience IO bottleneck in SQL Server.
You should collect windows and SQL server performance counters as well if
you suspect such a problem.
The primary solution to IO problems are: 1)configure files and filegroups in
your database so that you can use your existing disk volumes better; 2) get
better hardware. SQL Server automatically issues the optimal IO size depends
on your file/filegroup configuration.
--
Wei Xiao [MSFT]
SQL Server Storage Engine Development
http://blogs.msdn.com/weix
This posting is provided "AS IS" with no warranties, and confers no rights.
"Michael C#" <xyz@.abcdef.com> wrote in message
news:E3BZd.4121$So4.369@.fe10.lga...
> That's good to know. Now I need to know I *can* do with the SQLIO
results.[vbcol=seagreen]
> So far the only use I've found is to print out hard copies so I'll always
> have something handy to wrap raw fish with.
> "wei xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
> news:eteDqvTKFHA.3336@.TK2MSFTNGP09.phx.gbl...
I/O's,[vbcol=seagreen]
sure[vbcol=seagreen]
(2003
>
|||Thanks for the feedback Wei. Unfortunately we've got top of the line
hardware and have configured the heck out of files and filegroups in the
database. In fact, SQL Server isn't the issue at all. We eliminated SQL
Server completely as a bottleneck. But my understanding was that SQLIO
measures the speed of the Disk I/O subsystem, not SQL Server, anyway.
Perhaps I read the documentation wrong. Anyways, I've decided that using
SQLIO is a dead end, so I'm on to other tools. Thanks.
"Wei Xiao [MSFT]" <weix@.online.microsoft.com> wrote in message
news:423cb5b4$1@.news.microsoft.com...
> SQLIO results can be useful if you experience IO bottleneck in SQL Server.
> You should collect windows and SQL server performance counters as well if
> you suspect such a problem.
> The primary solution to IO problems are: 1)configure files and filegroups
> in
> your database so that you can use your existing disk volumes better; 2)
> get
> better hardware. SQL Server automatically issues the optimal IO size
> depends
> on your file/filegroup configuration.
> --
> --
> Wei Xiao [MSFT]
> SQL Server Storage Engine Development
> http://blogs.msdn.com/weix
>
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Michael C#" <xyz@.abcdef.com> wrote in message
> news:E3BZd.4121$So4.369@.fe10.lga...
> results.
> I/O's,
> sure
> (2003
>