Unable allocate min server memory size to greater than 1GB


    Sponsored Links


  • 1. Users cannot logon to applcation using Windows Authentication unless their account is inside the SQL Server local admin group
    Gurus, Running SQL server 2005 SP2 configured for Windows Authentication on a two-node cluster running Windows Server 2003 SP2 inside a single Active Directory domain. All users logon to the domain from their Windows XP Pro workstations. On the SQL Server is an application to which some users must access. When they bring up the logon screen for this application, there is a radio button for SQL Authentication and another Windows Authentication. The users cannot logon using Windows Authentication unless their domain account is a member of the local administrators group on the SQL Server. Note: Even if I give their domain accounts 'sysadmin' role on the DB server, they still cannot login into the application using Windows Authentication until they given local administrator privileges on the DB server. -- Spin
  • 2. Microsoft Update display update category for uninstalled product
    I have uninstalled SQL server express edition from my computer, may be the uninstalled is not clean, because i can't reinstall the database with the name MSSQLSERVER So i give up to try to reinstall the SQL server But from the Windows Update, it still display "SQL Server feature Pack" i just still have C++ redistribute
  • 3. SQL Server 2005 Express Question - Cross Post
    I have purchased a dedicated server from GoDaddy. Ive installed MS-SQL Express 2005 to be used for an internal application. Windows 2003 Firewall Turned Off (just until i figure this problem out) I cannot connect to the database from remote. Ive tried everything ive read about (turning on remote connections, etc) and am still having no luck. GoDaddy wont help because i didnt purchase their managed services. Is there something else im missing? Is this a setup issue, or something particular with a GoDaddy dedicated server? Should SQL 2005 EXPRESS allow this type of connection? TIA Tim
  • 4. Very odd data loss in SQL Server 2005
    Hi there. I'm experiencing a very odd data loss in my SQL Server 2005. Some data records have just gone missing (about 140 rows in one of the tables) and I can't see any pattern. Also it seems to be, that this problem affects only 2 tables but I'm not sure about that since I haven't checked everything. Right now I trying to find out when the data has started to be missing, but I right now it looks like the is a coherence with a database shrink I did on Wednesday. Is that even possible? This isn't the first shrink I did on a database. Is it even possible that this odd kind of data loss is the result of a problem in SQL Server. Right now, I doubt it. I hope that it helps, that I have a complete chain of transaction protocols since the last good database. I hope I can restore a consistent database with these. Well before that I have find out what happened. The eventlog shows nothing and my next candidate is the sys.messages. If you have any ideas about this error or where and how to look for the reson, I'd be very happy to hear (read ;-) ) from you. CU and thanks in advance, Sven
  • 5. Please help with automated data import from ODBC
    SQL Server 2005 Standard Edition. Using wizard, no problem to use SQL to import from ODBC data source. Saved the DTS job to an SSIS package, unable to use with agent scheduler. Error is DTS_E_PRODUCTLEVELTOLOW. Please help why is this happening?

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 70 guest