Unable allocate min server memory size to greater than 1GB


    Sponsored Links


  • 1. Job Agent - Syntax Errors
    Hi All, I'm having a problem with a job on an SQL 2000 Server that is linked to pull data from an SQL 2005 server. When I enter my infromation into the Job Step properties and parse the SQL, the system tells me it is fine. When I run the code through query analyzer, it also works fine as well. However, when the job is run, I am getting a syntax error on the file name because (I think) it is in double quotes. Here is the SQL I am trying to parse: insert into starscream.NAPROD_40.dbo."SPS 4_0$AFON DTS Import Staging" (vin,productionDateDT,plantcode,UnitReferenceNo,ProductionLotNo, KDLotNo,LotPosition,MTOC,ModelGrade,Returned,Completed,GhostBody) select a.vin, (CONVERT(varchar(10), a.pdate ,101) + ' ' + CONVERT(varchar(10), a.ptime ,108)), a.plantcode, a.lrnum, a.prod_lot, a.kd_lot, a.lot_position, a.mtoc, 'N/A', 'N/A', 'N/A','N/A' from bos_data a where vin COLLATE DATABASE_DEFAULT not in (select vin from starscream.NAPROD_40.dbo."SPS 4_0$AFON DTS Import Staging") Again, it fails with a syntax error on the "SPS 4_0$AFON DTS Import Staging" in both areas of the SQL. Any ideas would be most appreciated. Thanks! Brian.
  • 2. Character greater than 'z'
    I've searched and have not found any good answers to this. Maybe there isn't one... I need to have a string that when sorted with an ORDER BY, it comes after the letter 'z'. The database is created with the collation SQL_Latin1_General_CP1_CI_AS. I know it is best to not rely on this and use some sort of surrogate field to order the rows, but I cannot do that in this case - the data is being used by SharePoint (MOSS) in a Business Data Catalog (BDC) column. SharePoint will sort one of it's lists by the BDC column value, but it sorts only by the values in that column. In ASCII, I could use the tilde (~), but SQL is putting the tilde first in the results. Is there any character I could put at the beginning of the string so it would fall out last in the query results? (Remember, it is SharePoint generating the query, so I cannot change the SQL it uses. I only control the values in the column.)
  • 3. Running SQL2005 profiler from an SQLAgent job
    Hi, I would like to run a certain profiler template against a server on a regular basis. I can run profiler90 from the Command Prompt and it starts creating the trace file. Can I run profiler90 from within an SQLAgent job? I have tried and it did not run. Thanks Chris
  • 4. changing table ownership
    Did something change with the sp_changeobject owner with SQL2005. The command does not seem to work. I am looking to change the owner of all the tbale of a SQL2005 database. Is there a quick way to do it? Thanks.
  • 5. tempdb log won't truncate
    SQL 2005, sometime last week, the transaction log for tempdb started growing at a slow but steady rate. We restarted SQL Server, no effect. There are no open transactions, I can force the log to truncate with a shrinkfile, but left to itself, the amount of space used will just keep growing, eventually forcing the file to autogrow, and I assume it would eventually fill up the disk. Appreciate any thoughts, thanks.

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.unable to allocate minimum server memory

Hello All,

I have a cluster of two nodes running Windows 2003 Enterprise Edition with 
SQL Server 2000 Enterprise. Each node has 32 GB. And I set the  max server 
memory and min server memory to 28 GB, but the maximum memory was shown only 
16 GB, and SQL Server reports "unable to allocation minimum server memory". 
PAE is in the boot.ini and AWE is enabled in the SQL Server. Any idea?

Thanks in advances

4.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

5.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.

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

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

8. Table Size greater than DB size ?



Who is online

Users browsing this forum: No registered users and 28 guest