Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Data Warehousing / September 2004

Tip: Looking for answers? Try searching our database.

SQL Server 2000 Freeze Memory

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Orlando - 15 Jun 2004 21:33 GMT
Hello there, my datawarehouse uses SQL 2000 enterprise as
database. When the ETL process runs it takes all the
memory of my server (aprox 2gb) and when it finish, the
memory stay freeze, an the task manager shows that the
MSSQL still using the memory and this takes a long time,
so I have to use the NET STOP to free the resources and
memory. What can provocate this situation?
Nate Shedd - 16 Jun 2004 14:57 GMT
You may be allowing SQL Server to use too much memory on your server. We had
a similar problem with processing Analysis Services cubes. On the SQL Server
Properties dialog Memory tab, set the Maximum (MB) to less than the full
amount. For example, if the slider has a range from 4MB to 2048MB, you could
set it to 1500MB.

> Hello there, my datawarehouse uses SQL 2000 enterprise as
> database. When the ETL process runs it takes all the
[quoted text clipped - 3 lines]
> so I have to use the NET STOP to free the resources and
> memory. What can provocate this situation?
Adrian Edwards - 18 Sep 2004 15:48 GMT
I know this is 3 months old but the answer is just wrong. SQL Server
should be setup to dynamically use memory, which is what appears to be
happening. When the ETL process needs more RAM it asks Windows which
duly allocates until all RAM has been used. SQL Server does not
automatically return the memory unless Windows explicitly asks for
blocks of memory. If Windows does not need the memory then SQL server
keeps it. This is by design and makes logical sense on a SQL box after
all who else wants the memory. No-one, so why keep sending messages
between SQL and Windows asking for more memory one minute and then
handing it back the next. Overhead NOT REQUIRED.

Adrian

> You may be allowing SQL Server to use too much memory on your server. We had
> a similar problem with processing Analysis Services cubes. On the SQL Server
[quoted text clipped - 9 lines]
>>so I have to use the NET STOP to free the resources and
>>memory. What can provocate this situation?
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.