Unable allocate min server memory size to greater than 1GB


    Sponsored Links


  • 1. what to be cautious when adding index to a large table
    Hello: We have a table that has millions of rows. I have added two columns recently, one is a varchar field and one is an integer field. If I want to add index to these two columns, anything I shall be aware of? Any idea as to the time it takes (roughly) to add the index? Thanks, Q
  • 2. SQL 2005 64 bit standard edition on 8 processor box
    Hi I am thinking of buying some new 8 64-bit processor boxes to run SQL server 2005 64 bit edition. I don't need the extra functionality of SQL 2005 Enterprise, and therefore would prefer to use SQL 2005 64bit standard edition. However, standard edition is limited to 4 CPUs. If I install 2 instances of SQL 2005 standard edition, will each instance use 4 processors? In other words, by using 2 instances will all 8 processors be fully utilized by sql server? If so, would that configuration comply with SQL server standard edition licensing? Thanks for helping with this question
  • 3. Query database on linked server where database has name like [ABC.DEF]
    A database exists on a linked server that I would like to query When I run the following command SELECT * from [INSTANCE_NAME].[ABC.DEF].dbo.sysfiles -- Note the name of database has an "." in it (I cannot change this) I get the error Server: Msg 7357, Level 16, State 2, Line 1 Could not process object '"ABC.DEF"."dbo"."sysfiles"'. The OLE DB provider 'SQLOLEDB' indicates that the object has no columns. OLE DB error trace [Non-interface error: OLE DB provider unable to process object, since the object has no columnsProviderName='SQLOLEDB', Query="ABC.DEF"."dbo"."sysfiles"']. This query works on other databases on this instance and other instances. Does anybody have any ideas?
  • 4. Query Analyser/EM Windows Authentication Weirdness
    Hi, When I start QA or EM using windows authentication on my PC to connect to a server based SQL Server instance it is using the Windows UID of a server admin that I would use to connect to a server using Terminal Services (Remote Desktop) rather than my current windows UID. The admin uid is not a sqlserver user so authentication fails and access is denied. I cannot see any way to make it revert to using the actual uid of my session. I have reinstalled sql server on my desktop etc. 1. Has anyone seen this behaviour before? 2. Any fixes? Thanks in advance.

Unable allocate min server memory size to greater than 1GB

Postby Sm9lIE5hbQ » Thu, 30 Mar 2006 15:58:01 GMT

I have installed a SQL Sever 2000 Standard Edition with Service Pack 4 on a 
Windows 2003 Standard Server with 2GB memory. But it does not allow me to set 
 the min server memory size that is greater than 1GB.  Do any one know what 
the problem is ? Thx.

Re: Unable allocate min server memory size to greater than 1GB

Postby oj » Thu, 30 Mar 2006 17:52:18 GMT

do you get an error? can you set it via sp_configure? technically, your sql 
can use up to 2GB on win2k3 std. though, this would be unwise 'cuz you have 
to leave some for the OS.


Re: Unable allocate min server memory size to greater than 1GB

Postby QW5keSBQcmljZQ » Thu, 30 Mar 2006 23:30:03 GMT

Check the setting for 'max server memory'. 'min server memory' will not be 
allowed to exceed that. Also, with /3gb enabled, 1gb is reserved for the 
Windows kernel. Ensure that in your boot.ini that /3gb or /pae are NOT 
enabled as 2gb of RAM is too low to be using those options (both eat more 
free memory for the extra memory structures).

Andy Price,
Sr. Database Administrator,
MCDBA 2003

Re: Unable allocate min server memory size to greater than 1GB

Postby Q2hpIEh1bmc » Fri, 31 Mar 2006 11:58:02 GMT

I represent Joe Nam to revise the question.
1. our sql server have set "use a fixed memory size" to 1800M, since the 
total memory of sql server exist 2G.
2. We don't know why the usage of physical memory only allocate below 1G of 
Please kindly advise the problem of our sql server setting.
Thank you for all advanced experts.
Chi Hung

Similar Threads:

1.unable to allocate 'min server memory'

I have SQL2000 Enterprise running on a Win2003 Enterprise machine, with 16GB
of ram....and no other applications. I start the database up and get an
error "unable to allocate 'min server memory'", which doesn't allow the DB
to startup unless I bring the setting down to around 1GB.. Any idea why this
would occur, if I have this much ram?

Thanks for your help

2.Warning: unable to allocate 'min server memory'

I have a Win2k3 EE server with SQL2000EE with 8GB of RAM. /PAE and /3GB
are enabled as well as AWE. Max mem is set to 6144 as is min however
after a reset of the server this warning is appearing:
Warning: unable to allocate 'min server memory'

3.SQL2005: Unable to allocate enough memory to start 'Query Processor'

Hi All,

I am using SQL Server 2005. It was working fine.
However all of a sudden I am getting following error.

It fails to start the MSSQLSERVER and SQL Server Agent services with and
error: The request failed or the service did not respond in a timely
fashion. Consult the event log or other applicable error logs for details.

In the log I discover other error:

  a.. Unable to allocate enough memory to start 'Query Processor'. Reduce
non-essential memory load or increase system memory.
Any help or pointer?

Thanks in advance

4.max server memory and min server memory (MB) setting

should these parameters be left to the server or should we set the min - max 
according to let's say 90 percent of phyisical memory.

5.Warning: unable to allocate 'min server memory' of 2000MB.

Are you using 2000 server or advanced server. The /3g is not supported in
2000 server
"Carrasco" < XXXX@XXXXX.COM > wrote in message
news: XXXX@XXXXX.COM ...
> Hi,
> I have a Windows 2000 Server with 4GB RAM, I set in the boot.ini file the
parameter multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microsoft Windows 2000
Server" /fastdetect /3GB
> In SQL I set min server memory to 2000 and Max server memory to 2800 -
When I restarted my machine when Sql started i received the following
message in the sql server log  Warning: unable to allocate 'min server
memory' of 2000MB.

6. Warning: unable to allocate 'min server memory' of 2258MB.

7. Table Size greater than DB size ?

8. Error setting the "min server memory" SQL Server 2000 parameter



Who is online

Users browsing this forum: No registered users and 2 guest