Make SQL use more memory

[usenet]

On Jun 21, 11:53 am, "Adam Machanic"
wrote:
> Do you have the /PAE switch enabled in boot.ini ?
>
> --
>
> Adam Machanic
> SQL Server MVP
>
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "dylan" wrote in message
>
> news:1182440393.064379.241090@p77g2000hsh.googlegr oups.com...
>
> > On Jun 21, 11:09 am, "Adam Machanic"
> > wrote:
> >> "dylan" wrote in message
>
> >>news:1182437032.054788.207030@n60g2000hse.googlegr oups.com...
>
> >> > Hmm, well according to this article
> >> >http://msdn2.microsoft.com/en-us/lib...3(SQL.90).aspx
> >> > AWE is not needed and cannot be configured on 64-bit operating systems.
>
> >> AWE is needed for 32-bit SQL Server, whether running on a 32-bit or
> >> 64-bit operating system. Lock Pages in Memory is only needed for 64-bit
> >> SQL
> >> Server. You're running 32-bit SQL Server, according to your first post?
>
> >> --
>
> >> Adam Machanic
> >> SQL Server MVP
>
> >> Author, "Expert SQL Server 2005
> >> Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>
> > I really need to read these things better, I didn't see in your
> > previous post that you were talking about Enterprise Edition SQL
> > Server, I thought you meant 64 Bit Windows 2003 Enterprise Edition.
> > Yes, I am running 32 bit SQL Server Standard on 32 Bit Windows 2003
> > Enterprise. Given that, I can't get AWE to enable. When I try to
> > enable it, I get the following error:
>
> > Alter Failed (Microsoft.SQLServer.SMO)
> > Additional information
> > + An exception occured while executing a Transact-SQL statement or
> > batch.
> > (Microsoft.SQLServer.ConnectionInfo)
> > + Address Windowing Extensions (AWE) requires the "lock pages in
> > memory" privilege which is not currently present in the access token
> > of the process.
>
> > When I looked that up, I found that I needed to enable the Enable the
> > Lock Pages in Memory Option. Using this article
> >http://msdn2.microsoft.com/en-us/lib...(SQL.90).aspxI tried
> > to do that, but it is still not working. Any insight?
>
> > Thanks very much for your help.

Yes I do.

[usenet]

Can you go into gpedit and make sure the perms are set properly, then go
back out to a command prompt, run gpupdate, and try again?

--

Adam Machanic
SQL Server MVP

Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220



"dylan" wrote in message
news:1182442259.823849.93310@q75g2000hsh.googlegro ups.com...
> On Jun 21, 11:53 am, "Adam Machanic"
> wrote:
>> Do you have the /PAE switch enabled in boot.ini ?
>>
>> --
>>
>> Adam Machanic
>> SQL Server MVP
>>
>> Author, "Expert SQL Server 2005
>> Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>>
>> "dylan" wrote in message
>>
>> news:1182440393.064379.241090@p77g2000hsh.googlegr oups.com...
>>
>> > On Jun 21, 11:09 am, "Adam Machanic"
>> > wrote:
>> >> "dylan" wrote in message
>>
>> >>news:1182437032.054788.207030@n60g2000hse.googlegr oups.com...
>>
>> >> > Hmm, well according to this article
>> >> >http://msdn2.microsoft.com/en-us/lib...3(SQL.90).aspx
>> >> > AWE is not needed and cannot be configured on 64-bit operating
>> >> > systems.
>>
>> >> AWE is needed for 32-bit SQL Server, whether running on a 32-bit
>> >> or
>> >> 64-bit operating system. Lock Pages in Memory is only needed for
>> >> 64-bit
>> >> SQL
>> >> Server. You're running 32-bit SQL Server, according to your first
>> >> post?
>>
>> >> --
>>
>> >> Adam Machanic
>> >> SQL Server MVP
>>
>> >> Author, "Expert SQL Server 2005
>> >> Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>>
>> > I really need to read these things better, I didn't see in your
>> > previous post that you were talking about Enterprise Edition SQL
>> > Server, I thought you meant 64 Bit Windows 2003 Enterprise Edition.
>> > Yes, I am running 32 bit SQL Server Standard on 32 Bit Windows 2003
>> > Enterprise. Given that, I can't get AWE to enable. When I try to
>> > enable it, I get the following error:
>>
>> > Alter Failed (Microsoft.SQLServer.SMO)
>> > Additional information
>> > + An exception occured while executing a Transact-SQL statement or
>> > batch.
>> > (Microsoft.SQLServer.ConnectionInfo)
>> > + Address Windowing Extensions (AWE) requires the "lock pages in
>> > memory" privilege which is not currently present in the access token
>> > of the process.
>>
>> > When I looked that up, I found that I needed to enable the Enable the
>> > Lock Pages in Memory Option. Using this article
>> >http://msdn2.microsoft.com/en-us/lib...(SQL.90).aspxI tried
>> > to do that, but it is still not working. Any insight?
>>
>> > Thanks very much for your help.
>
> Yes I do.
>

[usenet]

On Jun 21, 12:20 pm, "Adam Machanic"
wrote:
> Can you go into gpedit and make sure the perms are set properly, then go
> back out to a command prompt, run gpupdate, and try again?
>
> --
>
> Adam Machanic
> SQL Server MVP
>
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>
> "dylan" wrote in message
>
> news:1182442259.823849.93310@q75g2000hsh.googlegro ups.com...
>
> > On Jun 21, 11:53 am, "Adam Machanic"
> > wrote:
> >> Do you have the /PAE switch enabled in boot.ini ?
>
> >> --
>
> >> Adam Machanic
> >> SQL Server MVP
>
> >> Author, "Expert SQL Server 2005
> >> Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>
> >> "dylan" wrote in message
>
> >>news:1182440393.064379.241090@p77g2000hsh.googlegr oups.com...
>
> >> > On Jun 21, 11:09 am, "Adam Machanic"
> >> > wrote:
> >> >> "dylan" wrote in message
>
> >> >>news:1182437032.054788.207030@n60g2000hse.googlegr oups.com...
>
> >> >> > Hmm, well according to this article
> >> >> >http://msdn2.microsoft.com/en-us/lib...3(SQL.90).aspx
> >> >> > AWE is not needed and cannot be configured on 64-bit operating
> >> >> > systems.
>
> >> >> AWE is needed for 32-bit SQL Server, whether running on a 32-bit
> >> >> or
> >> >> 64-bit operating system. Lock Pages in Memory is only needed for
> >> >> 64-bit
> >> >> SQL
> >> >> Server. You're running 32-bit SQL Server, according to your first
> >> >> post?
>
> >> >> --
>
> >> >> Adam Machanic
> >> >> SQL Server MVP
>
> >> >> Author, "Expert SQL Server 2005
> >> >> Development"http://www.apress.com/book/bookDisplay.html?bID=10220
>
> >> > I really need to read these things better, I didn't see in your
> >> > previous post that you were talking about Enterprise Edition SQL
> >> > Server, I thought you meant 64 Bit Windows 2003 Enterprise Edition.
> >> > Yes, I am running 32 bit SQL Server Standard on 32 Bit Windows 2003
> >> > Enterprise. Given that, I can't get AWE to enable. When I try to
> >> > enable it, I get the following error:
>
> >> > Alter Failed (Microsoft.SQLServer.SMO)
> >> > Additional information
> >> > + An exception occured while executing a Transact-SQL statement or
> >> > batch.
> >> > (Microsoft.SQLServer.ConnectionInfo)
> >> > + Address Windowing Extensions (AWE) requires the "lock pages in
> >> > memory" privilege which is not currently present in the access token
> >> > of the process.
>
> >> > When I looked that up, I found that I needed to enable the Enable the
> >> > Lock Pages in Memory Option. Using this article
> >> >http://msdn2.microsoft.com/en-us/lib...90).aspxItried
> >> > to do that, but it is still not working. Any insight?
>
> >> > Thanks very much for your help.
>
> > Yes I do.

Well, that's part of the issue, I guess. It says "add an account with
privileges to run sqlservr.exe" - by that does it mean to add the
account that the MSSQLSERVER service starts as, or an account that has
sysadmin rights to the SQL Server?

[usenet]

"dylan" wrote in message
news:1182446047.108936.106190@w5g2000hsg.googlegro ups.com...
>
> Well, that's part of the issue, I guess. It says "add an account with
> privileges to run sqlservr.exe" - by that does it mean to add the
> account that the MSSQLSERVER service starts as, or an account that has
> sysadmin rights to the SQL Server?

The account that the SQL Server service runs as.


--

Adam Machanic
SQL Server MVP

Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220

[usenet]

On Jun 21, 1:17 pm, "Adam Machanic"
wrote:
> "dylan" wrote in message
>
> news:1182446047.108936.106190@w5g2000hsg.googlegro ups.com...
>
>
>
> > Well, that's part of the issue, I guess. It says "add an account with
> > privileges to run sqlservr.exe" - by that does it mean to add the
> > account that the MSSQLSERVER service starts as, or an account that has
> > sysadmin rights to the SQL Server?
>
> The account that the SQL Server service runs as.
>
> --
>
> Adam Machanic
> SQL Server MVP
>
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220

I still get the same error. Does it matter that I'm not logging into
the SQL Server as the account that starts the service?

[usenet]

"dylan" wrote in message
news:1182447460.877712.292450@n60g2000hse.googlegr oups.com...
>
> I still get the same error. Does it matter that I'm not logging into
> the SQL Server as the account that starts the service?

No, that shouldn't be an issue. Did you try rebooting? I'm wondering
if the policy isn't being applied for some reason.

Also, if you look in Task Manager, is SQL Server running using the
account that you think it should be using?


--

Adam Machanic
SQL Server MVP

Author, "Expert SQL Server 2005 Development"
http://www.apress.com/book/bookDisplay.html?bID=10220

[usenet]

On Jun 21, 2:12 pm, "Adam Machanic"
wrote:
> "dylan" wrote in message
>
> news:1182447460.877712.292450@n60g2000hse.googlegr oups.com...
>
>
>
> > I still get the same error. Does it matter that I'm not logging into
> > the SQL Server as the account that starts the service?
>
> No, that shouldn't be an issue. Did you try rebooting? I'm wondering
> if the policy isn't being applied for some reason.
>
> Also, if you look in Task Manager, is SQL Server running using the
> account that you think it should be using?
>
> --
>
> Adam Machanic
> SQL Server MVP
>
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220

[usenet]

On Jun 21, 2:12 pm, "Adam Machanic"
wrote:
> "dylan" wrote in message
>
> news:1182447460.877712.292450@n60g2000hse.googlegr oups.com...
>
>
>
> > I still get the same error. Does it matter that I'm not logging into
> > the SQL Server as the account that starts the service?
>
> No, that shouldn't be an issue. Did you try rebooting? I'm wondering
> if the policy isn't being applied for some reason.
>
> Also, if you look in Task Manager, is SQL Server running using the
> account that you think it should be using?
>
> --
>
> Adam Machanic
> SQL Server MVP
>
> Author, "Expert SQL Server 2005 Development"http://www.apress.com/book/bookDisplay.html?bID=10220

I haven't tried rebooting, I can't do that until tonight, but I will
try that. I know sometimes Computer Configuration policies do not
take effect until after rebooting. I checked, and the SQL Server is
running as the account I expect it to be.

[usenet]

Do you see "Address Windowing Extensions enabled" in the message log?


> I haven't tried rebooting, I can't do that until tonight, but I will
> try that. I know sometimes Computer Configuration policies do not
> take effect until after rebooting. I checked, and the SQL Server is
> running as the account I expect it to be.
>

[usenet]

On Jun 22, 12:14 pm, "Terri" wrote:
> Do you see "Address Windowing Extensions enabled" in the message log?
>
> > I haven't tried rebooting, I can't do that until tonight, but I will
> > try that. I know sometimes Computer Configuration policies do not
> > take effect until after rebooting. I checked, and the SQL Server is
> > running as the account I expect it to be.

Hi Terri,
I'm not sure what you mean by the message log?