Drop Table
Support Forum for database administrators and web based access to important newsgroups related to databasesHi Prado, I have a very similar configuration/situation and still can not see more than 2.4 GB of memory allocated to SQL Server. By the way, the sql service account has the "lock pages in memory". Any help will be greatly appreciated. Kamal. "Prado" wrote: > Hi again, > > finally, we have discovered the problem, the user account that starts SQL > Services didn't have rights of "Lock Page in Memory" on the local policy. We > changed this issue and after restarting the services SQL runs correctly. Y ou > can see more information about it in the next link > http://msdn.microsoft.com/library/d...erver_1fnd.asp. > > Thanks you all, > > Prado > > > "Tom Moreau" escribió: >
Post Follow-up to this messageHi, I'm sorry but I don't remember all the tests that we made, but one of the tests was change the position of the parameters /PAE and /3GB in the boot.ini. Another suggestions from a spanish discussion groups was to be sure that the parameter "max memory size" in SQL have a fixed value because dinamicall y doesn't work fine with SQL 2000 and all the memory must be take it when the service start. Somebody spoke about a bug with the number of the value, depends if the value was odd or pair. Here you have the link to this discuss http://groups.google.es/group/micro...9559 7f1 Also, you can check the SQL Server counter for Target Memory Server, here you can check the maximum memory recognized by SQL Server. I hope that this can help you. Good luck. Regards, Prado "Kamal Hassan" wrote: > Hi Prado, > > I have a very similar configuration/situation and still can not see more > than 2.4 GB of memory allocated to SQL Server. > > By the way, the sql service account has the "lock pages in memory". > > Any help will be greatly appreciated. > > Kamal. > > > > "Prado" wrote: >
Post Follow-up to this message
Show a Printable Version
Email This Page to Someone!
Receive updates to this thread