AWE /3GB performance

I have 8gb of memory, win2003 server advanced, sql server 2000 ent. The
concern when using the 3gb option is that I force the OS into 1gb of memory
and causing the OS to be memory starved. Is it possible to create this
condition and what would be the minimum set of services that should be
running on the SQL Server box. For example, print spooler, application layer
gateway, etc.
"Uri Dimant" wrote:

> John
> If you have Windows 2000(Advanced or Datacenter) and 4GB RAM use /3GB (AWE
> support isn't used)
> You can provide more info to get more accurate advice
> "John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
> news:617A3083-DBEA-46C4-AFBE-C501839D12C7@.microsoft.com...
>
>
John
>The /3GB switch is used to tell SQL Server to take advantage of 3GB out of
>the base 4GB of RAM that Windows 2000/3 supports natively. If you don't
>specify >this option, then SQL Server will only take advantage of 2GB of
>the first 4GB of RAM in the server, essentially wasting 1GB of RAM.
http://www.sql-server-performance.com/awe_memory.asp
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:A6CF4DB6-FFEE-4AA0-82B8-DD3BB04E6D74@.microsoft.com...[vbcol=seagreen]
>I have 8gb of memory, win2003 server advanced, sql server 2000 ent. The
> concern when using the 3gb option is that I force the OS into 1gb of
> memory
> and causing the OS to be memory starved. Is it possible to create this
> condition and what would be the minimum set of services that should be
> running on the SQL Server box. For example, print spooler, application
> layer
> gateway, etc.
>
> "Uri Dimant" wrote:
|||Uri, thanks for the info. I have read the doc and understand AWE and the 3gb
option. Also I noticed some more advanced boot.ini options to control the
use of the memory above 1g.
I have a sql server that is running slow. I have not been able to profile
the server. What I want to understand is "Is it possible to cause the OS to
be memory starved using the 3gb option causing sql server to appear slow?"
For example if the OS is forced to swap to disk for normal OS activities.
If it is possible what would be the telling signs?
thanks
"Uri Dimant" wrote:

> John
> http://www.sql-server-performance.com/awe_memory.asp
>
>
> "John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
> news:A6CF4DB6-FFEE-4AA0-82B8-DD3BB04E6D74@.microsoft.com...
>
>
|||John
Is it SQL Server running dedicated on the server?
Do you have an OLTP applications connect to the SQL Server?
I'd strat to to identify perfomance problems from the application side (
checking indexes, database design)
"John Grant" <JohnGrant@.discussions.microsoft.com> wrote in message
news:DD6405A3-56C5-4394-81D5-121D204420F3@.microsoft.com...[vbcol=seagreen]
> Uri, thanks for the info. I have read the doc and understand AWE and the
> 3gb
> option. Also I noticed some more advanced boot.ini options to control the
> use of the memory above 1g.
> I have a sql server that is running slow. I have not been able to profile
> the server. What I want to understand is "Is it possible to cause the OS
> to
> be memory starved using the 3gb option causing sql server to appear slow?"
> For example if the OS is forced to swap to disk for normal OS activities.
> If it is possible what would be the telling signs?
> thanks
> "Uri Dimant" wrote:

average download rates for SQL Server

I have a SQL Server hosted on a Win2003 server. I have a monitor on the server letting me know the average download speeds. When I do a large select from a remote connection, it looks like the download rate maxes out at around 10 kb/sec.

Is this an average download rate for a server hosting sql server?
actually it looks like the 2003 servers download (via FTP at least) is much much faster. Is there a different configuration for SQL Server that could be limiting the download? I'm really just assuming that the download is limited because when I do a very large select from a remote computer, it takes around 30 seconds, but the download rate never goes above 10 kb/sec.

|||My first impression would be to verify that some network segment is not limiting to 10 MB.|||Your transfer rates will be limited to the transfer rate of the network or the speed of the hard drives.