Using Two motch memory  
Author Message
Major_Dave





PostPosted: Wed Jan 04 06:45:47 CST 2006 Top

SQL Server Developer >> Using Two motch memory

Hello there

I have database on one of my clients that has 2.7 Gb on the data

On normal hours sql server usege is approx 1.85Gb

The sql in the is standard edition.

And it works very slow

Does it normal that 70% of the database is on the RAM and what i need to do
to improve performance?

SQL Server183  
 
 
David





PostPosted: Wed Jan 04 06:45:47 CST 2006 Top

SQL Server Developer >> Using Two motch memory
> Hello there
>
> I have database on one of my clients that has 2.7 Gb on the data
>
> On normal hours sql server usege is approx 1.85Gb
>
> The sql in the is standard edition.
>
> And it works very slow
>
> Does it normal that 70% of the database is on the RAM and what i need to do
> to improve performance?

SQL Server will use as much RAM as is available to it. If your database
server is shared by other applications or used as a file server then
you may want to allocate some smaller portion of RAM to SQL Server but
on a dedicated server it's better to let SQL use as much RAM as it can.
Caheing data in RAM improves performance.

How To Troubleshoot Application Performance with SQL Server:
http://support.microsoft.com/default.aspx?scid=kb;en-us;224587

--
David Portas
SQL Server MVP
--

 
 
Ryan





PostPosted: Wed Jan 04 06:46:47 CST 2006 Top

SQL Server Developer >> Using Two motch memory By default SQL memory allocation is set to dynamic. SQL Server will take as
much memory as it needs.

Start by having a look at this article :-
http://www.sql-server-performance.com/q&a115.asp

--
HTH. Ryan




> Hello there
>
> I have database on one of my clients that has 2.7 Gb on the data
>
> On normal hours sql server usege is approx 1.85Gb
>
> The sql in the is standard edition.
>
> And it works very slow
>
> Does it normal that 70% of the database is on the RAM and what i need to
> do to improve performance?
>


 
 
Enric





PostPosted: Wed Jan 04 06:50:04 CST 2006 Top

SQL Server Developer >> Using Two motch memory hi Roy.

It depends a lof of circumstances and variables. But in any case it is not
normal.

On the strength the lack of info I suppose that doing a good maintenance
plan (including shrink of course), allocating non-cluster indexin separte
filegroups and so on...



> Hello there
>
> I have database on one of my clients that has 2.7 Gb on the data
>
> On normal hours sql server usege is approx 1.85Gb
>
> The sql in the is standard edition.
>
> And it works very slow
>
> Does it normal that 70% of the database is on the RAM and what i need to do
> to improve performance?
>
>
>
 
 
David





PostPosted: Wed Jan 04 06:59:20 CST 2006 Top

SQL Server Developer >> Using Two motch memory

> hi Roy.
>
> It depends a lof of circumstances and variables. But in any case it is not
> normal.
>
> On the strength the lack of info I suppose that doing a good maintenance
> plan (including shrink of course)

Shrinking log or data files should NOT be part of a good maintenance plan in
most cases. It certainly is not something you should do regularly anyway.
See:
http://www.karaszi.com/SQLServer/info_dont_shrink.asp

--
David Portas
SQL Server MVP
--


 
 
David





PostPosted: Wed Jan 04 11:54:59 CST 2006 Top

SQL Server Developer >> Using Two motch memory
> Hello there
>
> I have database on one of my clients that has 2.7 Gb on the data
>
> On normal hours sql server usege is approx 1.85Gb
>
> The sql in the is standard edition.
>
> And it works very slow
>
> Does it normal that 70% of the database is on the RAM and what i need
> to do to improve performance?

Unless you have other services that require more memory than what's
available, the memory is not likely the problem. As others have replied,
SQL Server will consume memory when needed and not give it back to the
OS unless necessary. This is by design and important for database
performance (better to get data from memory than disk). Have a look at
your SQL and try and determine what's not running efficiently. You're
problem is likely there.

If your OS and other running services are memory starved, then set SQL
Server to use a fixed maximum amount of memory.


--
David Gugick
Quest Software
www.quest.com