<div>
You probably have a bottleneck at your drive controller or the drives themselves. &nbsp;Turn on performance monitoring of your storage volumes and monitor your users activity around the times the queue averges 100% - This will help point you to where improvements are needed, be it faster harder, more cache, or whatever.
</div>


<div>
&quot;faster harder should have been &quot;faster hardware&quot;
</div>


<div>
Ok i did notice I cant increase the page file on the server. Do I need the /3GB switch for that?
</div>


<div>
The /3GB switch is to allow windows to use more physical memory if you have the memory to support it. &nbsp;Do you have 4 GB of memory?<br />
<br />
What is your page file size and utilization?
</div>


<div>
it wont let me make the page file biger that 4096
</div>


<div>
Press &lt;Ctrl&gt;+&lt;Shift&gt;+&lt;Esc&gt;, then go into the Performance tab.<br />
<br />
What is showing as:<br />
&nbsp; &nbsp;Total Memory<br />
&nbsp; &nbsp;Available<br />
&nbsp; &nbsp;System Cache<br />
&nbsp; &nbsp;PF Usage<br />

</div>


<div>
in order;<br />
<br />
3669384 total mem<br />
1447106 available<br />
945376 system cache<br />
1.96gb PF usage
</div>


<div>
Making your paging file larger would not help this issue. &nbsp;Have you started performance monitoring on SQL, controller, and the volumes?
</div>


<div>
It wont let me make the paging file any bigger that 4096
</div>


<div>
Thank you that is what I needed. 
</div>


<div>
<div class="content wysiwyg-content">
I have SQL 2000 server that is at 100% avg disk que all day. Can tell me why the que would be so high? thanks
</div>
</div>


I have SQL 2000 server that is at 100% avg disk que all day. Can tell me why the que would be so high? thanks

You probably have a bottleneck at your drive controller or the drives themselves.  Turn on performance monitoring of your storage volumes and monitor your users activity around the times the queue averges 100% - This will help point you to where improvements are needed, be it faster harder, more cache, or whatever.

&quot;faster harder should have been &quot;faster hardware&quot;

Ok i did notice I cant increase the page file on the server. Do I need the /3GB switch for that?

The /3GB switch is to allow windows to use more physical memory if you have the memory to support it.  Do you have 4 GB of memory?

What is your page file size and utilization?

it wont let me make the page file biger that 4096

Press &lt;Ctrl&gt;+&lt;Shift&gt;+&lt;Esc&gt;, then go into the Performance tab.

What is showing as:
   Total Memory
   Available
   System Cache
   PF Usage


in order;

3669384 total mem
1447106 available
945376 system cache
1.96gb PF usage

Making your paging file larger would not help this issue.  Have you started performance monitoring on SQL, controller, and the volumes?

It wont let me make the paging file any bigger that 4096

Avg disk ques at 100% all day

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).