Unable allocate min server memory size to greater than 1GB


    Sponsored Links


  • 1. Issue with Invoice Table generating same invoice number
    Hi, I an it issues invoice # 99new to SQL and have a problem with our application which is a web based written on ASP. During the selection to create the invoice it returns invoice # 100000 which I thought was fine but after generating more invoices they are all generating with the same invoice number which is 100000 The ASP code has the following select statement Select MAX(invoicenum)as num from invoices(NOLOCK) where invoicenum > '60000' and isnumeric(invoicenum) =1. This has a result of 99999 which now I can see why the next invoice # is 100000. I've look at the table columns and the invoicenum has a field length of 20. Also I took a look at the table size which have the following sizes. Rows=40981 Reserved=15400KB data=7488KB index size=696KB unused=7216KB. Can someone help on how I can resolve this problem eith within SQL statement or the table itself. Thank You Tony, IT Administrator
  • 2. Extracting data from operational databases
    Hi all, A very good day to all of you. Currently, i am working on data warehouse. I had been reading on it. Data warehouse is make up of relational views, am i right to say that? How should i go about creating views from the operational databases and stored the views in the warehouse? Cheers Poy Ling
  • 3. SPs or Application level logic?
    Hi. I'm *quite* new and am starting to design/write a lot of SPs in MSSQL 2005. I have been advised by some colleagues to reduce the logic in my SPs and move it to the application level. Currently, my design puts *all* of my business logic in SPs. My reasoning was centralised business logic that all frontends (in diff languages if required) can use -> less errors and easier maintanance etc. Estimate project size is about 150 SPs, 50 tables. Please give me your thoughts. Again, (from thoughts passed by my colleages) I need to confirm that MSSQL 2005 has no issues with the following 1) Nested SP execution. (SPs calling SPs calling SPs etc ) 2) Nested transactions entered through Nested SP execution (1) 3) Raising errors that can be passed to the client rolling back nested transactions (2) On a separate note, can some confirm that Database Mail services work on MSSQL 2005 Express? I've read contradicting articles (works, not works). In my case, it just sits in the queue. I have checked my smpt and it can send fine. I have done recommended stuff to check the problem (stop/start) but it just sits in the queue (status: unsent). What gives? Best Regards Riyaz
  • 4. using XQuery to add separator to query results
    I have this XML from MSDN declare @x xml set @x = ' <People> <Person> <Name>John</Name> <Age>24</Age> </Person> <Person> <Name>JGoofy</Name> <Age>34</Age> </Person> <Person> <Name>Daffy</Name> <Age>30</Age> </Person> </People> ' select @x.query('/People/Person[contains(Name[1], "J") and xs:integer(Age[1]) < 40]/Name/text()') Query returns JohnJGoofy How do I make it "John;JGoofy"? I will still be working on this but your help will be highly appreciated.

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