| Groups | Blog | Home |
sql server clustering : SQL Server 2000 AWE on Windows 2003 64bit
2000 service pack 4 with the following hotfix http://support.microsoft.com/default.aspx?kbid=899761. I am trying to enable the AWE support to take advantage of my 8 gigs of memory. I have currently ran the sp_configure 'awe enabled', 1 to enable the AWE within SQL then I applied the above hotfix. Here is where it seems that something is not right after the reboot within the windows task manager on the performance tab the page file usgae is at close to 8 gigs however when I look at the processes and look at how much SQL server is using it only says around 100mg. This doesn't seem correct before changing to AWE SQl Server would usually use up almost 4 gigs. One additional note that I have let it run for about a week now and the memory does not leave the 100 or so megs. Does anyone have any ideas on this? thanks Chris cfrank@investorforce.com
Saravanan thanks for your response...
The Windows 2003 is 64 bit however SQL Server 2000 is 32 bit which correct me if I am wrong it cannot use more than 4 gigs of memory without AWE enabled. thanks Chris [quoted text, click to view] Saravanan Palanivelu wrote:
> I don't think you need AWE to use all the 8 gig in 64 bit installtion. > because 64 bit can address with out AWE upto 16 TB ( I think windows 2003 > limit is -512 GB ) > > http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc#_Toc68085560 > > Regards, > Saravanan > > > "Chris" <cfrank@investorforce.com> wrote in message > news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... > >I currently am running a Windows 2003 64 bit server with SQL Server > > 2000 service pack 4 with the following hotfix > > http://support.microsoft.com/default.aspx?kbid=899761. I am trying to > > enable the AWE support to take advantage of my 8 gigs of memory. I > > have currently ran the sp_configure 'awe enabled', 1 to enable the AWE > > within SQL then I applied the above hotfix. Here is where it seems > > that something is not right after the reboot within the windows task > > manager on the performance tab the page file usgae is at close to 8 > > gigs however when I look at the processes and look at how much SQL > > server is using it only says around 100mg. This doesn't seem correct > > before changing to AWE SQl Server would usually use up almost 4 gigs. > > One additional note that I have let it run for about a week now and the > > memory does not leave the 100 or so megs. Does anyone have any ideas > > on this? > > > > thanks > > Chris > > cfrank@investorforce.com > >
I don't think you need AWE to use all the 8 gig in 64 bit installtion.
because 64 bit can address with out AWE upto 16 TB ( I think windows 2003 limit is -512 GB ) http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc#_Toc68085560 Regards, Saravanan [quoted text, click to view] "Chris" <cfrank@investorforce.com> wrote in message news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... >I currently am running a Windows 2003 64 bit server with SQL Server > 2000 service pack 4 with the following hotfix > http://support.microsoft.com/default.aspx?kbid=899761. I am trying to > enable the AWE support to take advantage of my 8 gigs of memory. I > have currently ran the sp_configure 'awe enabled', 1 to enable the AWE > within SQL then I applied the above hotfix. Here is where it seems > that something is not right after the reboot within the windows task > manager on the performance tab the page file usgae is at close to 8 > gigs however when I look at the processes and look at how much SQL > server is using it only says around 100mg. This doesn't seem correct > before changing to AWE SQl Server would usually use up almost 4 gigs. > One additional note that I have let it run for about a week now and the > memory does not leave the 100 or so megs. Does anyone have any ideas > on this? > > thanks > Chris > cfrank@investorforce.com >
Thanks...In the perfmon it does show it using the almost 8 gigs what a
relief...Last question is there a way to see the same numbers in SQL? [quoted text, click to view] Chris wrote:
> Saravanan thanks for your response... > > The Windows 2003 is 64 bit however SQL Server 2000 is 32 bit which > correct me if I am wrong it cannot use more than 4 gigs of memory > without AWE enabled. > > > thanks > Chris > > > Saravanan Palanivelu wrote: > > I don't think you need AWE to use all the 8 gig in 64 bit installtion. > > because 64 bit can address with out AWE upto 16 TB ( I think windows 2003 > > limit is -512 GB ) > > > > http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc#_Toc68085560 > > > > Regards, > > Saravanan > > > > > > "Chris" <cfrank@investorforce.com> wrote in message > > news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... > > >I currently am running a Windows 2003 64 bit server with SQL Server > > > 2000 service pack 4 with the following hotfix > > > http://support.microsoft.com/default.aspx?kbid=899761. I am trying to > > > enable the AWE support to take advantage of my 8 gigs of memory. I > > > have currently ran the sp_configure 'awe enabled', 1 to enable the AWE > > > within SQL then I applied the above hotfix. Here is where it seems > > > that something is not right after the reboot within the windows task > > > manager on the performance tab the page file usgae is at close to 8 > > > gigs however when I look at the processes and look at how much SQL > > > server is using it only says around 100mg. This doesn't seem correct > > > before changing to AWE SQl Server would usually use up almost 4 gigs. > > > One additional note that I have let it run for about a week now and the > > > memory does not leave the 100 or so megs. Does anyone have any ideas > > > on this? > > > > > > thanks > > > Chris > > > cfrank@investorforce.com > > >
[quoted text, click to view]
> Last question is there a way to see the same numbers in SQL? You can query these SQL perfmon counter values in T-SQL from master..sysperfinfo Linchi [quoted text, click to view] "Chris" wrote:
> Thanks...In the perfmon it does show it using the almost 8 gigs what a > relief...Last question is there a way to see the same numbers in SQL? > > > Chris wrote: > > Saravanan thanks for your response... > > > > The Windows 2003 is 64 bit however SQL Server 2000 is 32 bit which > > correct me if I am wrong it cannot use more than 4 gigs of memory > > without AWE enabled. > > > > > > thanks > > Chris > > > > > > Saravanan Palanivelu wrote: > > > I don't think you need AWE to use all the 8 gig in 64 bit installtion. > > > because 64 bit can address with out AWE upto 16 TB ( I think windows 2003 > > > limit is -512 GB ) > > > > > > http://download.microsoft.com/download/0/4/7/047da8d3-aa80-452a-9148-40a7e8a7048a/SQL64bitAdvantages.doc#_Toc68085560 > > > > > > Regards, > > > Saravanan > > > > > > > > > "Chris" <cfrank@investorforce.com> wrote in message > > > news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... > > > >I currently am running a Windows 2003 64 bit server with SQL Server > > > > 2000 service pack 4 with the following hotfix > > > > http://support.microsoft.com/default.aspx?kbid=899761. I am trying to > > > > enable the AWE support to take advantage of my 8 gigs of memory. I > > > > have currently ran the sp_configure 'awe enabled', 1 to enable the AWE > > > > within SQL then I applied the above hotfix. Here is where it seems > > > > that something is not right after the reboot within the windows task > > > > manager on the performance tab the page file usgae is at close to 8 > > > > gigs however when I look at the processes and look at how much SQL > > > > server is using it only says around 100mg. This doesn't seem correct > > > > before changing to AWE SQl Server would usually use up almost 4 gigs. > > > > One additional note that I have let it run for about a week now and the > > > > memory does not leave the 100 or so megs. Does anyone have any ideas > > > > on this? > > > > > > > > thanks > > > > Chris > > > > cfrank@investorforce.com > > > > >
Task Manager processes pane doesn't really know what AWE is and so reports
incorrect numbers. If you look at the SQLServer:Memory Manager Total Server Memory(KB) counter it should give you the right number -- HTH, Jasper Smith (SQL Server MVP) http://www.sqldbatips.com [quoted text, click to view] "Chris" <cfrank@investorforce.com> wrote in message news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... >I currently am running a Windows 2003 64 bit server with SQL Server > 2000 service pack 4 with the following hotfix > http://support.microsoft.com/default.aspx?kbid=899761. I am trying to > enable the AWE support to take advantage of my 8 gigs of memory. I > have currently ran the sp_configure 'awe enabled', 1 to enable the AWE > within SQL then I applied the above hotfix. Here is where it seems > that something is not right after the reboot within the windows task > manager on the performance tab the page file usgae is at close to 8 > gigs however when I look at the processes and look at how much SQL > server is using it only says around 100mg. This doesn't seem correct > before changing to AWE SQl Server would usually use up almost 4 gigs. > One additional note that I have let it run for about a week now and the > memory does not leave the 100 or so megs. Does anyone have any ideas > on this? > > thanks > Chris > cfrank@investorforce.com >
And to extend this, AWE usage shows as page file usage in task manager, so
you are using all of the available memory. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Jasper Smith" <jasper_smith9@hotmail.com> wrote in message news:%23$AU5X5yGHA.4576@TK2MSFTNGP06.phx.gbl... > Task Manager processes pane doesn't really know what AWE is and so reports > incorrect numbers. If you look at the SQLServer:Memory Manager Total > Server Memory(KB) counter it should give you the right number > > -- > HTH, > Jasper Smith (SQL Server MVP) > http://www.sqldbatips.com > > > "Chris" <cfrank@investorforce.com> wrote in message > news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... >>I currently am running a Windows 2003 64 bit server with SQL Server >> 2000 service pack 4 with the following hotfix >> http://support.microsoft.com/default.aspx?kbid=899761. I am trying to >> enable the AWE support to take advantage of my 8 gigs of memory. I >> have currently ran the sp_configure 'awe enabled', 1 to enable the AWE >> within SQL then I applied the above hotfix. Here is where it seems >> that something is not right after the reboot within the windows task >> manager on the performance tab the page file usgae is at close to 8 >> gigs however when I look at the processes and look at how much SQL >> server is using it only says around 100mg. This doesn't seem correct >> before changing to AWE SQl Server would usually use up almost 4 gigs. >> One additional note that I have let it run for about a week now and the >> memory does not leave the 100 or so megs. Does anyone have any ideas >> on this? >> >> thanks >> Chris >> cfrank@investorforce.com >> > >
Does windows 2003 64 bit have AWE?
(My understanding - it doesn't, because the 64-bit windows 2003 OS can directly address the memory up to 1 TB, in theory 16 TB) Since Chris is enabling the AWE in SQL Server 2000 (32 bit) under Windows 2003 64 bit. How is the SQL Server memory management is going to work? Will it be able to use the memory beyond 4 GB? Thanks Saravanan. [quoted text, click to view] "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message news:Omo5v2EzGHA.4580@TK2MSFTNGP05.phx.gbl... > And to extend this, AWE usage shows as page file usage in task manager, so > you are using all of the available memory. > > -- > Geoff N. Hiten > Senior Database Administrator > Microsoft SQL Server MVP > > > > > "Jasper Smith" <jasper_smith9@hotmail.com> wrote in message > news:%23$AU5X5yGHA.4576@TK2MSFTNGP06.phx.gbl... >> Task Manager processes pane doesn't really know what AWE is and so >> reports incorrect numbers. If you look at the SQLServer:Memory Manager >> Total Server Memory(KB) counter it should give you the right number >> >> -- >> HTH, >> Jasper Smith (SQL Server MVP) >> http://www.sqldbatips.com >> >> >> "Chris" <cfrank@investorforce.com> wrote in message >> news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... >>>I currently am running a Windows 2003 64 bit server with SQL Server >>> 2000 service pack 4 with the following hotfix >>> http://support.microsoft.com/default.aspx?kbid=899761. I am trying to >>> enable the AWE support to take advantage of my 8 gigs of memory. I >>> have currently ran the sp_configure 'awe enabled', 1 to enable the AWE >>> within SQL then I applied the above hotfix. Here is where it seems >>> that something is not right after the reboot within the windows task >>> manager on the performance tab the page file usgae is at close to 8 >>> gigs however when I look at the processes and look at how much SQL >>> server is using it only says around 100mg. This doesn't seem correct >>> before changing to AWE SQl Server would usually use up almost 4 gigs. >>> One additional note that I have let it run for about a week now and the >>> memory does not leave the 100 or so megs. Does anyone have any ideas >>> on this? >>> >>> thanks >>> Chris >>> cfrank@investorforce.com >>> >> >> > >
AWE is an application-level way to address >2GB of RAM. The corresponding
system-level function is PAE. No, the 64-bit OS does not have PAE, but it does support the AWE APIs for 32-bit applications. The "glue" code for that was included in SQL 2000 SP4. Just as on a 32-bit platform, memory above 2GB is non-addressable and usable only for data cache for SQL 2000. SQL 2005 native 64-bit mode can address all the memory on a 64-bit OS. -- Geoff N. Hiten Senior Database Administrator Microsoft SQL Server MVP [quoted text, click to view] "Saravanan Palanivelu" <saravanan_p@hotmail.com> wrote in message news:e5CgMZGzGHA.3280@TK2MSFTNGP02.phx.gbl... > Does windows 2003 64 bit have AWE? > > (My understanding - it doesn't, because the 64-bit windows 2003 OS can > directly address the memory up to 1 TB, in theory 16 TB) > > > > > > Since Chris is enabling the AWE in SQL Server 2000 (32 bit) under Windows > 2003 64 bit. How is the SQL Server memory management is going to work? > > > > Will it be able to use the memory beyond 4 GB? > > > > Thanks > > Saravanan. > > > > > > > > > "Geoff N. Hiten" <SQLCraftsman@gmail.com> wrote in message > news:Omo5v2EzGHA.4580@TK2MSFTNGP05.phx.gbl... >> And to extend this, AWE usage shows as page file usage in task manager, >> so you are using all of the available memory. >> >> -- >> Geoff N. Hiten >> Senior Database Administrator >> Microsoft SQL Server MVP >> >> >> >> >> "Jasper Smith" <jasper_smith9@hotmail.com> wrote in message >> news:%23$AU5X5yGHA.4576@TK2MSFTNGP06.phx.gbl... >>> Task Manager processes pane doesn't really know what AWE is and so >>> reports incorrect numbers. If you look at the SQLServer:Memory Manager >>> Total Server Memory(KB) counter it should give you the right number >>> >>> -- >>> HTH, >>> Jasper Smith (SQL Server MVP) >>> http://www.sqldbatips.com >>> >>> >>> "Chris" <cfrank@investorforce.com> wrote in message >>> news:1156859280.061091.202390@h48g2000cwc.googlegroups.com... >>>>I currently am running a Windows 2003 64 bit server with SQL Server >>>> 2000 service pack 4 with the following hotfix >>>> http://support.microsoft.com/default.aspx?kbid=899761. I am trying to >>>> enable the AWE support to take advantage of my 8 gigs of memory. I >>>> have currently ran the sp_configure 'awe enabled', 1 to enable the AWE >>>> within SQL then I applied the above hotfix. Here is where it seems >>>> that something is not right after the reboot within the windows task >>>> manager on the performance tab the page file usgae is at close to 8 >>>> gigs however when I look at the processes and look at how much SQL >>>> server is using it only says around 100mg. This doesn't seem correct >>>> before changing to AWE SQl Server would usually use up almost 4 gigs. >>>> One additional note that I have let it run for about a week now and the >>>> memory does not leave the 100 or so megs. Does anyone have any ideas >>>> on this? >>>> >>>> thanks >>>> Chris >>>> cfrank@investorforce.com >>>> >>> >>> >> >> > >
I agree with Geoff. An additional note, if you are running SQL Server 2000 32 bit on a Windows Server 2003 64 bit OS, then SQL Server can access upto 4GB of memory without any switches (note that if the OS was 32
bit then SQL can access upto 2GB without any switches). For more than 4GB, in this scenario, you will enable AWE and set "max server memory" to 8GB. I hope you have more thatn 8GB RAM as you do not want to give everything to SQL Server. If you just have 8GB RAM then I will set "max server memory" to 6GB or 6.5GB max. If you do not set "max server memory", SQL will take all the RAM - 128MB which is not recommended for obvious reasons. When AWE is enabled, you cannot use Task Manager. This is documented in Books Online The following is from Books Online Use System Monitor (Performance Monitor in Microsoft Windows NT® 4.0) to retrieve information on SQL Server memory usage and available memory. Task Manager does not provide accurate memory usage information for AWE. Therefore, the memory quoted for sqlservr.exe is not correct. To obtain the correct amount of SQL Server memory usage, you can use the Total Server Memory (KB) performance counter, activated through System Monitor, or select the memory usage from sysperfinfo. For more information, see Monitoring Memory Usage. Additionally you can run "dbcc memorystatus" to Monitor SQL Server Memory Usage. For additional information on this dbcc command, see Microsoft Knowledge base article INF: Using DBCC MEMORYSTATUS to Monitor SQL Server Memory Usage http://support.microsoft.com/?id=271624 HTH, Best Regards, Uttam Parui Microsoft Corporation This posting is provided "AS IS" with no warranties, and confers no rights. Are you secure? For information about the Strategic Technology Protection Program and to order your FREE Security Tool Kit, please visit http://www.microsoft.com/security. Microsoft highly recommends that users with Internet access update their Microsoft software to better protect against viruses and security vulnerabilities. The easiest way to do this is to visit the following websites: http://www.microsoft.com/protect http://www.microsoft.com/security/guidance/default.mspx
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |