|
sql
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
32 bit SQL Server on 64 bit OS
According to the specifications SQL Server 2005 Standard Edition can use
"Operating system maximum" RAM. Does this mean that it can use all memory of a machine running 64-bit Windows Server 2003 with 16 Gb RAM? If so, are there any special settings required to access all memory? Regards; /jb Dear Jonny,
Good morning! By default 32-bit SQL Server can consume at most 2GB memory on 32-bit OS, but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit consume the 16GB memory, you can enable AWE on your SQL Server 2005 32-bit and set the max server memory to 16GB: sp_configure 'show advanced options',1 go reconfigure sp_configure 'awe enabled',1 go reconfigure sp_configure 'max server memory', 16384 go reconfigure after you set the max server memory, you need to restart your SQL Server instance to take it effect. For more information, please refer to this article: Enabling AWE Memory for SQL Server http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx If you are using SQL Server 2005 64-bit, you do not need to enable AWE. It will fully take advantage of 64-bit. Please do not hesitate to let me know if you have any other questions or concerns. Thank you! Best regards, Charles Wang Microsoft Online Community Support Get Secure! - www.microsoft.com/security ==================================================== When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue. ==================================================== This posting is provided "AS IS" with no warranties, and confers no rights. ==================================================== Thanks!
Regards; /jb ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i meddelandet Show quoteHide quote news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... > Dear Jonny, > Good morning! > > By default 32-bit SQL Server can consume at most 2GB memory on 32-bit OS, > but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit > consume the 16GB memory, you can enable AWE on your SQL Server 2005 32-bit > and set the max server memory to 16GB: > sp_configure 'show advanced options',1 > go > reconfigure > sp_configure 'awe enabled',1 > go > reconfigure > sp_configure 'max server memory', 16384 > go > reconfigure > > after you set the max server memory, you need to restart your SQL Server > instance to take it effect. For more information, please refer to this > article: > Enabling AWE Memory for SQL Server > http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx > > If you are using SQL Server 2005 64-bit, you do not need to enable AWE. It > will fully take advantage of 64-bit. > > Please do not hesitate to let me know if you have any other questions or > concerns. Thank you! > > Best regards, > Charles Wang > > Microsoft Online Community Support > Get Secure! - www.microsoft.com/security > ==================================================== > When responding to posts, please "Reply to Group" via your newsreader so > that others may learn and benefit from your issue. > ==================================================== > This posting is provided "AS IS" with no warranties, and confers no > rights. > ==================================================== > > > > > > To add to what has been said, there really is no reason to run 32-bit on
64-bit hardware. The only reason I have found is when you are required to setup a linked server to a system that does not have a 64-bit ODBC/OLEDB driver available. Show quoteHide quote "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... > Thanks! > > Regards; > /jb > > ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i > meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >> Dear Jonny, >> Good morning! >> >> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit OS, >> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >> 32-bit >> and set the max server memory to 16GB: >> sp_configure 'show advanced options',1 >> go >> reconfigure >> sp_configure 'awe enabled',1 >> go >> reconfigure >> sp_configure 'max server memory', 16384 >> go >> reconfigure >> >> after you set the max server memory, you need to restart your SQL Server >> instance to take it effect. For more information, please refer to this >> article: >> Enabling AWE Memory for SQL Server >> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >> >> If you are using SQL Server 2005 64-bit, you do not need to enable AWE. >> It >> will fully take advantage of 64-bit. >> >> Please do not hesitate to let me know if you have any other questions or >> concerns. Thank you! >> >> Best regards, >> Charles Wang >> >> Microsoft Online Community Support >> Get Secure! - www.microsoft.com/security >> ==================================================== >> When responding to posts, please "Reply to Group" via your newsreader so >> that others may learn and benefit from your issue. >> ==================================================== >> This posting is provided "AS IS" with no warranties, and confers no >> rights. >> ==================================================== >> >> >> >> >> >> > How about the stupid fact that you have to purchase a completely new license
when migrating from 32 to 64-bit versions of SQL Server? There is no upgrade path at all available. Regards; /jb Show quoteHide quote "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... > To add to what has been said, there really is no reason to run 32-bit on > 64-bit hardware. The only reason I have found is when you are required to > setup a linked server to a system that does not have a 64-bit ODBC/OLEDB > driver available. > > "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message > news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... >> Thanks! >> >> Regards; >> /jb >> >> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i >> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >>> Dear Jonny, >>> Good morning! >>> >>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit >>> OS, >>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >>> 32-bit >>> and set the max server memory to 16GB: >>> sp_configure 'show advanced options',1 >>> go >>> reconfigure >>> sp_configure 'awe enabled',1 >>> go >>> reconfigure >>> sp_configure 'max server memory', 16384 >>> go >>> reconfigure >>> >>> after you set the max server memory, you need to restart your SQL Server >>> instance to take it effect. For more information, please refer to this >>> article: >>> Enabling AWE Memory for SQL Server >>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >>> >>> If you are using SQL Server 2005 64-bit, you do not need to enable AWE. >>> It >>> will fully take advantage of 64-bit. >>> >>> Please do not hesitate to let me know if you have any other questions or >>> concerns. Thank you! >>> >>> Best regards, >>> Charles Wang >>> >>> Microsoft Online Community Support >>> Get Secure! - www.microsoft.com/security >>> ==================================================== >>> When responding to posts, please "Reply to Group" via your newsreader so >>> that others may learn and benefit from your issue. >>> ==================================================== >>> This posting is provided "AS IS" with no warranties, and confers no >>> rights. >>> ==================================================== >>> >>> >>> >>> >>> >>> >> That is not my understanding. The 64 and 32 bit versions should be the same
cost. If you go from 2000 32 to 2005 64 then sure but 2005 32 to 2005 64 should not be an issue. -- Show quoteHide quoteAndrew J. Kelly SQL MVP Solid Quality Mentors "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message news:eOnNePv%23JHA.3544@TK2MSFTNGP04.phx.gbl... > How about the stupid fact that you have to purchase a completely new > license when migrating from 32 to 64-bit versions of SQL Server? There is > no upgrade path at all available. > > Regards; > /jb > > "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet > news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... >> To add to what has been said, there really is no reason to run 32-bit on >> 64-bit hardware. The only reason I have found is when you are required >> to setup a linked server to a system that does not have a 64-bit >> ODBC/OLEDB driver available. >> >> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >> news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... >>> Thanks! >>> >>> Regards; >>> /jb >>> >>> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i >>> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >>>> Dear Jonny, >>>> Good morning! >>>> >>>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit >>>> OS, >>>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >>>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >>>> 32-bit >>>> and set the max server memory to 16GB: >>>> sp_configure 'show advanced options',1 >>>> go >>>> reconfigure >>>> sp_configure 'awe enabled',1 >>>> go >>>> reconfigure >>>> sp_configure 'max server memory', 16384 >>>> go >>>> reconfigure >>>> >>>> after you set the max server memory, you need to restart your SQL >>>> Server >>>> instance to take it effect. For more information, please refer to this >>>> article: >>>> Enabling AWE Memory for SQL Server >>>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >>>> >>>> If you are using SQL Server 2005 64-bit, you do not need to enable AWE. >>>> It >>>> will fully take advantage of 64-bit. >>>> >>>> Please do not hesitate to let me know if you have any other questions >>>> or >>>> concerns. Thank you! >>>> >>>> Best regards, >>>> Charles Wang >>>> >>>> Microsoft Online Community Support >>>> Get Secure! - www.microsoft.com/security >>>> ==================================================== >>>> When responding to posts, please "Reply to Group" via your newsreader >>>> so >>>> that others may learn and benefit from your issue. >>>> ==================================================== >>>> This posting is provided "AS IS" with no warranties, and confers no >>>> rights. >>>> ==================================================== >>>> >>>> >>>> >>>> >>>> >>>> >>> > It is the same cost, but my license provider says I can't swap a SQL Server
2005 32 bit license for a 64 bit license, but need to purchase a new license. Regards; /jb Show quoteHide quote "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> skrev i meddelandet news:%23h0Y7fx%23JHA.1376@TK2MSFTNGP02.phx.gbl... > That is not my understanding. The 64 and 32 bit versions should be the > same cost. If you go from 2000 32 to 2005 64 then sure but 2005 32 to 2005 > 64 should not be an issue. > > -- > Andrew J. Kelly SQL MVP > Solid Quality Mentors > > > "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message > news:eOnNePv%23JHA.3544@TK2MSFTNGP04.phx.gbl... >> How about the stupid fact that you have to purchase a completely new >> license when migrating from 32 to 64-bit versions of SQL Server? There is >> no upgrade path at all available. >> >> Regards; >> /jb >> >> "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet >> news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... >>> To add to what has been said, there really is no reason to run 32-bit on >>> 64-bit hardware. The only reason I have found is when you are required >>> to setup a linked server to a system that does not have a 64-bit >>> ODBC/OLEDB driver available. >>> >>> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >>> news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... >>>> Thanks! >>>> >>>> Regards; >>>> /jb >>>> >>>> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i >>>> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >>>>> Dear Jonny, >>>>> Good morning! >>>>> >>>>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit >>>>> OS, >>>>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >>>>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >>>>> 32-bit >>>>> and set the max server memory to 16GB: >>>>> sp_configure 'show advanced options',1 >>>>> go >>>>> reconfigure >>>>> sp_configure 'awe enabled',1 >>>>> go >>>>> reconfigure >>>>> sp_configure 'max server memory', 16384 >>>>> go >>>>> reconfigure >>>>> >>>>> after you set the max server memory, you need to restart your SQL >>>>> Server >>>>> instance to take it effect. For more information, please refer to this >>>>> article: >>>>> Enabling AWE Memory for SQL Server >>>>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >>>>> >>>>> If you are using SQL Server 2005 64-bit, you do not need to enable >>>>> AWE. It >>>>> will fully take advantage of 64-bit. >>>>> >>>>> Please do not hesitate to let me know if you have any other questions >>>>> or >>>>> concerns. Thank you! >>>>> >>>>> Best regards, >>>>> Charles Wang >>>>> >>>>> Microsoft Online Community Support >>>>> Get Secure! - www.microsoft.com/security >>>>> ==================================================== >>>>> When responding to posts, please "Reply to Group" via your newsreader >>>>> so >>>>> that others may learn and benefit from your issue. >>>>> ==================================================== >>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>> rights. >>>>> ==================================================== >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> >>>> >> > I would give MS a call and ask them. I think they are trying to scam you out
of some money but I can't find any documentation one way or the other. I don't have a setup disk here but I was under the impression the DVD had both the 32 and 64 bit versions on it so I don't see how they can require a different license. -- Show quoteHide quoteAndrew J. Kelly SQL MVP Solid Quality Mentors "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message news:ejvDDmy%23JHA.4984@TK2MSFTNGP05.phx.gbl... > It is the same cost, but my license provider says I can't swap a SQL > Server 2005 32 bit license for a 64 bit license, but need to purchase a > new license. > > Regards; > /jb > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> skrev i meddelandet > news:%23h0Y7fx%23JHA.1376@TK2MSFTNGP02.phx.gbl... >> That is not my understanding. The 64 and 32 bit versions should be the >> same cost. If you go from 2000 32 to 2005 64 then sure but 2005 32 to >> 2005 64 should not be an issue. >> >> -- >> Andrew J. Kelly SQL MVP >> Solid Quality Mentors >> >> >> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >> news:eOnNePv%23JHA.3544@TK2MSFTNGP04.phx.gbl... >>> How about the stupid fact that you have to purchase a completely new >>> license when migrating from 32 to 64-bit versions of SQL Server? There >>> is no upgrade path at all available. >>> >>> Regards; >>> /jb >>> >>> "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet >>> news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... >>>> To add to what has been said, there really is no reason to run 32-bit >>>> on 64-bit hardware. The only reason I have found is when you are >>>> required to setup a linked server to a system that does not have a >>>> 64-bit ODBC/OLEDB driver available. >>>> >>>> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >>>> news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... >>>>> Thanks! >>>>> >>>>> Regards; >>>>> /jb >>>>> >>>>> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i >>>>> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >>>>>> Dear Jonny, >>>>>> Good morning! >>>>>> >>>>>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit >>>>>> OS, >>>>>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >>>>>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >>>>>> 32-bit >>>>>> and set the max server memory to 16GB: >>>>>> sp_configure 'show advanced options',1 >>>>>> go >>>>>> reconfigure >>>>>> sp_configure 'awe enabled',1 >>>>>> go >>>>>> reconfigure >>>>>> sp_configure 'max server memory', 16384 >>>>>> go >>>>>> reconfigure >>>>>> >>>>>> after you set the max server memory, you need to restart your SQL >>>>>> Server >>>>>> instance to take it effect. For more information, please refer to >>>>>> this >>>>>> article: >>>>>> Enabling AWE Memory for SQL Server >>>>>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >>>>>> >>>>>> If you are using SQL Server 2005 64-bit, you do not need to enable >>>>>> AWE. It >>>>>> will fully take advantage of 64-bit. >>>>>> >>>>>> Please do not hesitate to let me know if you have any other questions >>>>>> or >>>>>> concerns. Thank you! >>>>>> >>>>>> Best regards, >>>>>> Charles Wang >>>>>> >>>>>> Microsoft Online Community Support >>>>>> Get Secure! - www.microsoft.com/security >>>>>> ==================================================== >>>>>> When responding to posts, please "Reply to Group" via your newsreader >>>>>> so >>>>>> that others may learn and benefit from your issue. >>>>>> ==================================================== >>>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>>> rights. >>>>>> ==================================================== >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>> >> > OK here is the proof that you can show to your shady vendor. The platform
does not matter so have a look here: http://www.microsoft.com/sqlserver/2008/en/us/licensing.aspx In particular you can find the link to the SQL Server Licensing Guide: http://download.microsoft.com/download/6/F/8/6F84A9FE-1E5C-44CC-87BB-C236BFCBA4DF/SQLServer2008_LicensingGuide.pdf Chapter 1 (Page 3) Diagram 1.1: SQL Server Licenses are Platform Independent SQL Server licenses and installation media allow you to install any platform of the licensed edition. -- Show quoteHide quoteAndrew J. Kelly SQL MVP Solid Quality Mentors "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message news:ejvDDmy%23JHA.4984@TK2MSFTNGP05.phx.gbl... > It is the same cost, but my license provider says I can't swap a SQL > Server 2005 32 bit license for a 64 bit license, but need to purchase a > new license. > > Regards; > /jb > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> skrev i meddelandet > news:%23h0Y7fx%23JHA.1376@TK2MSFTNGP02.phx.gbl... >> That is not my understanding. The 64 and 32 bit versions should be the >> same cost. If you go from 2000 32 to 2005 64 then sure but 2005 32 to >> 2005 64 should not be an issue. >> >> -- >> Andrew J. Kelly SQL MVP >> Solid Quality Mentors >> >> >> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >> news:eOnNePv%23JHA.3544@TK2MSFTNGP04.phx.gbl... >>> How about the stupid fact that you have to purchase a completely new >>> license when migrating from 32 to 64-bit versions of SQL Server? There >>> is no upgrade path at all available. >>> >>> Regards; >>> /jb >>> >>> "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet >>> news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... >>>> To add to what has been said, there really is no reason to run 32-bit >>>> on 64-bit hardware. The only reason I have found is when you are >>>> required to setup a linked server to a system that does not have a >>>> 64-bit ODBC/OLEDB driver available. >>>> >>>> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message >>>> news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... >>>>> Thanks! >>>>> >>>>> Regards; >>>>> /jb >>>>> >>>>> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i >>>>> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... >>>>>> Dear Jonny, >>>>>> Good morning! >>>>>> >>>>>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit >>>>>> OS, >>>>>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit >>>>>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 >>>>>> 32-bit >>>>>> and set the max server memory to 16GB: >>>>>> sp_configure 'show advanced options',1 >>>>>> go >>>>>> reconfigure >>>>>> sp_configure 'awe enabled',1 >>>>>> go >>>>>> reconfigure >>>>>> sp_configure 'max server memory', 16384 >>>>>> go >>>>>> reconfigure >>>>>> >>>>>> after you set the max server memory, you need to restart your SQL >>>>>> Server >>>>>> instance to take it effect. For more information, please refer to >>>>>> this >>>>>> article: >>>>>> Enabling AWE Memory for SQL Server >>>>>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx >>>>>> >>>>>> If you are using SQL Server 2005 64-bit, you do not need to enable >>>>>> AWE. It >>>>>> will fully take advantage of 64-bit. >>>>>> >>>>>> Please do not hesitate to let me know if you have any other questions >>>>>> or >>>>>> concerns. Thank you! >>>>>> >>>>>> Best regards, >>>>>> Charles Wang >>>>>> >>>>>> Microsoft Online Community Support >>>>>> Get Secure! - www.microsoft.com/security >>>>>> ==================================================== >>>>>> When responding to posts, please "Reply to Group" via your newsreader >>>>>> so >>>>>> that others may learn and benefit from your issue. >>>>>> ==================================================== >>>>>> This posting is provided "AS IS" with no warranties, and confers no >>>>>> rights. >>>>>> ==================================================== >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> >>>>> >>> >> > I'd report your license provider to Microsoft.
Sorry, but this does not sound right. Geoff Schaller Software Objectives Show quoteHide quote "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message news:ejvDDmy#JHA.4984@TK2MSFTNGP05.phx.gbl: > It is the same cost, but my license provider says I can't swap a SQL Server > 2005 32 bit license for a 64 bit license, but need to purchase a new > license. > > Regards; > /jb > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> skrev i meddelandet > news:%23h0Y7fx%23JHA.1376@TK2MSFTNGP02.phx.gbl... > > > That is not my understanding. The 64 and 32 bit versions should be the > > same cost. If you go from 2000 32 to 2005 64 then sure but 2005 32 to 2005 > > 64 should not be an issue. > > > > -- > > Andrew J. Kelly SQL MVP > > Solid Quality Mentors > > > > > > "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message > > news:eOnNePv%23JHA.3544@TK2MSFTNGP04.phx.gbl... > > >> How about the stupid fact that you have to purchase a completely new > >> license when migrating from 32 to 64-bit versions of SQL Server? There is > >> no upgrade path at all available. > >> > >> Regards; > >> /jb > >> > >> "Jeffrey Williams" <jeff.williams3***@verizon.net> skrev i meddelandet > >> news:OB$V5Lg9JHA.5040@TK2MSFTNGP04.phx.gbl... > > >>> To add to what has been said, there really is no reason to run 32-bit on > >>> 64-bit hardware. The only reason I have found is when you are required > >>> to setup a linked server to a system that does not have a 64-bit > >>> ODBC/OLEDB driver available. > >>> > >>> "Jonny Bergdahl" <jonnybergdahl@newsgroup.nospam> wrote in message > >>> news:#MY6zCX9JHA.4948@TK2MSFTNGP04.phx.gbl... > > >>>> Thanks! > >>>> > >>>> Regards; > >>>> /jb > >>>> > >>>> ""Charles Wang [MSFT]"" <chang***@online.microsoft.com> skrev i > >>>> meddelandet news:5ek5xrL9JHA.5192@TK2MSFTNGHUB02.phx.gbl... > > >>>>> Dear Jonny, > >>>>> Good morning! > >>>>> > >>>>> By default 32-bit SQL Server can consume at most 2GB memory on 32-bit > >>>>> OS, > >>>>> but 4GB memory on 64-bit OS. If you want your SQL Server 2005 32-bit > >>>>> consume the 16GB memory, you can enable AWE on your SQL Server 2005 > >>>>> 32-bit > >>>>> and set the max server memory to 16GB: > >>>>> sp_configure 'show advanced options',1 > >>>>> go > >>>>> reconfigure > >>>>> sp_configure 'awe enabled',1 > >>>>> go > >>>>> reconfigure > >>>>> sp_configure 'max server memory', 16384 > >>>>> go > >>>>> reconfigure > >>>>> > >>>>> after you set the max server memory, you need to restart your SQL > >>>>> Server > >>>>> instance to take it effect. For more information, please refer to this > >>>>> article: > >>>>> Enabling AWE Memory for SQL Server > >>>>> http://technet.microsoft.com/en-us/library/ms190673(SQL.90).aspx > >>>>> > >>>>> If you are using SQL Server 2005 64-bit, you do not need to enable > >>>>> AWE. It > >>>>> will fully take advantage of 64-bit. > >>>>> > >>>>> Please do not hesitate to let me know if you have any other questions > >>>>> or > >>>>> concerns. Thank you! > >>>>> > >>>>> Best regards, > >>>>> Charles Wang > >>>>> > >>>>> Microsoft Online Community Support > >>>>> Get Secure! - www.microsoft.com/security > >>>>> ==================================================== > >>>>> When responding to posts, please "Reply to Group" via your newsreader > >>>>> so > >>>>> that others may learn and benefit from your issue. > >>>>> ==================================================== > >>>>> This posting is provided "AS IS" with no warranties, and confers no > >>>>> rights. > >>>>> ==================================================== > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >> > > > I agree; these are not the type of licensing providers that we want around.
On 7/4/09 4:44 AM, in article xDE3m.2554$ze1.***@news-server.bigpond.net.au, Show quoteHide quote "Geoff Schaller" <geof***@softwareobjectivesxx.com.au> wrote: > I'd report your license provider to Microsoft. > Sorry, but this does not sound right. Dear all,
For licensing issue, you can call 1-800-426-9400, Monday through Friday, 6:00 A.M. to 6:00 P.M. (Pacific Time) to speak directly to a Microsoft licensing specialist, and you can get more detail information from there. Worldwide customers can use the Guide to Worldwide Microsoft Licensing Sites to find contact information in their locations. Thank you! Best regards, Charles Wang Microsoft Online Community Support ========================================================= Delighting our customers is our #1 priority. We welcome your comments and suggestions about how we can improve the support we provide to you. Please feel free to let my manager know what you think of the level of service provided. You can send feedback directly to my manager at: msd***@microsoft.com. ========================================================= This posting is provided "AS IS" with no warranties, and confers no rights. =========================================================  
Other interesting topics
SQL Timeout Error
Multiple databases performance Can I script out SQL Server jobs programmatically? setup a sql login which can only reset password kill the long run job automatically collation for multiple language in a column understanding metrics/performance SQL Server Import Export Wizard does not create table indexes Creating table Upsized tables problem [XPost from m.p.s.migrationassistant and m.p.s.newusers] |
|||||||||||||||||||||||
