Hi.
I have a Dell Server with Windows 2003 R2 SP2 64bit ,SQL Server 2005 SP2
(also 64Bit) and 12GB Ram. The Problem is, that the SQL Server Process only
allocates max 90-100MB. That's why big SQLs run very slow.

I checked the setup variables on the managment console and everything seems
to be ok. I don't know how to solve this problem.

Please help!

Ulf

Hopefully the following helps, check their recommedations:

http://www.microsoft.com/technet/pro...hysdbstor.mspx

http://www.microsoft.com/technet/pro...n/sqlops6.mspx


"Ulf Dingler" <u.dingler@lasartes.de> wrote in message
news:6fmabrFbskioU1@mid.uni-berlin.de...
> Hi.
> I have a Dell Server with Windows 2003 R2 SP2 64bit ,SQL Server 2005 SP2
> (also 64Bit) and 12GB Ram. The Problem is, that the SQL Server Process
> only allocates max 90-100MB. That's why big SQLs run very slow.
>
> I checked the setup variables on the managment console and everything
> seems to be ok. I don't know how to solve this problem.
>
> Please help!
>
> Ulf

Ulf Dingler (u.dingler@lasartes.de) writes:
> I have a Dell Server with Windows 2003 R2 SP2 64bit ,SQL Server 2005 SP2
> (also 64Bit) and 12GB Ram. The Problem is, that the SQL Server Process
> only allocates max 90-100MB. That's why big SQLs run very slow.
>
> I checked the setup variables on the managment console and everything
> seems to be ok. I don't know how to solve this problem.

What does "sp_configure 'max server memory'" report? And "sp_configure
'awe enabled'"?

Have you check in Task Manager whether there is any other process that
takes up a lot of memory?

How big are your databases?

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

"Erland Sommarskog" <esquel@sommarskog.se> schrieb im Newsbeitrag
news:Xns9AF0D6C2AFBYazorman@127.0.0.1...


> What does "sp_configure 'max server memory'" report? And "sp_configure
> 'awe enabled'"?
>
> Have you check in Task Manager whether there is any other process that
> takes up a lot of memory?
>

awe is enabled but i read, that awe is not important for 64bit. sp_configure
'max server memory' reports 2147483647. no other process takes more than
60mb and there is a lot of memory free (10GB) for the sql server process.

> How big are your databases?
>
the databases are very big. 7GB/9GB/70GB

Ulf Dingler (u.dingler@lasartes.de) writes:
> awe is enabled but i read, that awe is not important for 64bit.

That's correct. It's not supposed to have any effect at all, but it
does affect something, although I don't recall exactly what.

On 32-bit when you have AWE enabled, and look in task manager, you don't
see the true size of SQL Server, as the AWE memory is not included. Maybe
there is a similar effect on 64-bit? Could you run DBCC MEMORYSTATUS and
post the output?

> the databases are very big. 7GB/9GB/70GB

Ehum, 70GB could be called mediums-sized, but it does not really
qualify as "very big". Not that it matter here. Unless the data-access
pattern is very concentrated, it seems unlikely that SQL Server would
not need more memory than 100 MB.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

Ulf Dingler wrote:

> I have a Dell Server with Windows 2003 R2 SP2 64bit ,SQL Server 2005 SP2
> (also 64Bit) and 12GB Ram. The Problem is, that the SQL Server Process only
> allocates max 90-100MB. That's why big SQLs run very slow.
>
> I checked the setup variables on the managment console and everything seems
> to be ok. I don't know how to solve this problem.

You can force SQL's memory usage by setting minimum and maximum to the
same value (say 10 GB, leaving the other 2 GB for the other processes).