We have a three tier application running on two tiers. 1&2 running on
one server and a seperate server for the databases. On the database
server we are running Windows 2000 Server with 3Gb of RAM and Dual
1.8GHz Xeon Processors and SQL Standard 2000.

The memory for the SQL server never seems to go above 1.8Gb. Does
anyone have some suggestions about this or does anyone have some
information on how many Db's can be run on one server. Most of them
are relatively small with low activity.

Thanks a lot..

2 ways for SQL2000 to use more than 2GB memory on 32 bit:

1. Enable AWE
2. Specify /3gb Windows option in boot.ini. But this only allows server to
use up to 3GB.

And SQL2000r should be able to handle 450+ db with most of them having low
activities smoothly.

--
Gang He
Software Design Engineer
Microsoft SQL Server Storage Engine

This posting is provided "AS IS" with no warranties, and confers no rights.
<interflex (AT) hotmail (DOT) com> wrote

Hi Gang,

We are using the Standard version of SQL so I do not think that this
feature is available.

If I specify /3gb in the boot.ini will there be any room for SQL. The
server has a total of 3Gb. Right now the SQL server is using 1.84Gb of
memory. The programmers have written some code that uploads images to
the database as a blob and I am receiving error code:
Error: 17803, Severity: 20, State: 12 Insufficient memory available

Any ideas and thanks.

The /3gb option relates to the split between the user and kernel parts
of the 4GB virtual address space that all Windows applications,
including SQL Server, are given. Usually the split is 50/50 i.e. 2GB
user and 2GB kernel so the /3gb switch gives 3GB User and 1GB kernel.
Depending on what else the server is doing, only having 1GB for the
kernel can actually lead to performance problems of it own as the OS
has to restrict memory buffers etc. to keep within the 1GB limit.

The amount of physical memory is irrelevant in this context and I would
suggest that the answer to your blob problem might be either scaling up
to the Enterprise Edition of SQL Server and beefing up the server or,
possibly, compressing the blob data, or limiting it's size, as high up
the application stack as possible. i.e. if you were accepting
photographic images on a website then get the web server to compress
the images before sending them to the database or simly impose a limit.

I guess, as always, it is up to you to decide what the cost/benefits
are for your unique application...

Malcolm
www.dbghost.com
True Change Management for SQL Server

What is AWE?

Gang He [MSFT] wrote: