September 30, 2008 at 9:58 am
I have 2 SQL 2005 sp2 (standard ed.) instances on a Windows 2003 sp2 (R2 Enterprise ed.).
OS and SQL are both 32-bit.
RAM: 8 GB
PAE is enabled.
I have not configured max memory or AWE.
When I look at the running processes I see the 2 sql processes each taking up 2.5 GB of memory.
I always thought the absolute max virtual memory accessible to a SQL instance in a 32-bit environment is 2 GB, when AWE is not enabled.
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
September 30, 2008 at 10:19 am
Is the /3GB swith active? If so, this could explain it.
If not, then I am clueless.
Fraggle
September 30, 2008 at 10:26 am
Fraggle (9/30/2008)
Is the /3GB swith active? If so, this could explain it.If not, then I am clueless.
Fraggle
Thank you, that makes sense.
I'm looking for the boot.ini file but can't find it.
What is its default location?
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
September 30, 2008 at 10:31 am
To edit the boot.ini file...
1. Right-click My Computer, and then click Properties.
-or-
Click Start, click Run, type sysdm.cpl, and then click OK.
2. On the Advanced tab, click Settings under Startup and Recovery.
3. Under System Startup, click Edit.
September 30, 2008 at 10:35 am
It would be in the BOOT.INI.
Follow what Tim said above.
Fraggle.
September 30, 2008 at 10:36 am
Tim Peters (9/30/2008)
To edit the boot.ini file...1. Right-click My Computer, and then click Properties.
-or-
Click Start, click Run, type sysdm.cpl, and then click OK.
2. On the Advanced tab, click Settings under Startup and Recovery.
3. Under System Startup, click Edit.
Thank you, it turns out both the 3gb switch and PAE are enabled.
That would explain the bahavior, and I should have thought of that...
Thanks for the feedback!
__________________________________________________________________________________
SQL Server 2016 Columnstore Index Enhancements - System Views for Disk-Based Tables[/url]
Persisting SQL Server Index-Usage Statistics with MERGE[/url]
Turbocharge Your Database Maintenance With Service Broker: Part 2[/url]
September 30, 2008 at 10:38 am
Glad to help.
Fraggle
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply