Showing posts with label supports. Show all posts
Showing posts with label supports. Show all posts

Monday, March 26, 2012

How much memory can 32-bit SQL Server 2000 use on Windows Server 2003 Standard x64 Edition

I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
I have is how much can it address on Win2003 Standard x64? The full 32 GB?
Or does the x64 editions not support the AWE method that the 32-bit version
uses?
Thanks!
Paul
Mike,
I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is for Itanium. For x64,
you need to run 32 bit SQL server (which requires sp4 of SQL2K to be supported).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:Obp8hhkcFHA.220@.TK2MSFTNGP12.phx.gbl...
> You've mixed up SQL & Windows versions & editions in your question a
> little but I think I understand what you're getting at.
> You'd be wanting to run the 64 bit edition of SQL Server 2000
> (Enterprise) if you're planning on running it on a x64 version of
> Windows. Given that, max memory is not really a consideration anymore
> because 64 bit addressing works differently to 32 bit addressing and the
> 64 bit edition of SQL Server 2000 (Enterprise) can address up to 512GB
> of memory (no AWE needed anymore); 64-bit addressing has a theoretical
> limit of 18 Exabytes. So it's pretty much a case of how much memory can
> the OS present to SQL Server?
> Advantages of 64 bit SQL Server:
> http://www.microsoft.com/sql/64bit/p...Advantages.asp
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
>
> Paul Widner wrote:
>
|||Thanks for the confirmation, Mike. I also found below at the sp4 home page (which you probably seen,
but just in case):
"SQL Server 2000 Service Pack 4 (SP4) adds platform support for Microsoft Windows Server 2003 x64
Edition, allowing 32-bit SQL Server 2000 applications to run on 64-bit platforms using the Windows
on Windows emulator (WOW64). SP4 addresses specific issues discovered in SQL Server 2000 since its
ship date. SP4 is also the first service pack to service the 64-bit edition of SQL Server."
http://www.microsoft.com/sql/downloads/2000/sp4.mspx
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/p...fo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin>).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
>
> Tibor Karaszi wrote:
>
|||I'm guessing here but I think SQL2000 Enterprise should be able to access up
to 4GB on W2003 x64.
A 32bit app won't be able to access any more than 4GB on W2003 x64 because
you can't use PAE extensions, but I think as SQL 2000 is compiled to be
large memory aware it will be able to access more than 2GB.
Peter Lawton
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
>question I have is how much can it address on Win2003 Standard x64? The
>full 32 GB? Or does the x64 editions not support the AWE method that the
>32-bit version uses?
>
> Thanks!
> Paul
>
|||PMJI, but SQL2005 will run 64-bit on Windows x64, so I wouldn't rush out and
spend money on an Itanium system unless you really need the performance.
It's supposed to be released the week of Nov. 7th.
Mike Kruchten
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/p...fo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin>).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> Tibor Karaszi wrote:
>
|||Anyone know how I can go about getting an offical response from Microsoft in
regard to this?
Paul
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
> I'm guessing here but I think SQL2000 Enterprise should be able to access
> up to 4GB on W2003 x64.
> A 32bit app won't be able to access any more than 4GB on W2003 x64 because
> you can't use PAE extensions, but I think as SQL 2000 is compiled to be
> large memory aware it will be able to access more than 2GB.
> Peter Lawton
> "Paul Widner" <paul_widner@.hotmail.com> wrote in message
> news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>
|||Did anyone ever get an answer to this?
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:O1fHdVpcFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Anyone know how I can go about getting an offical response from Microsoft
in[vbcol=seagreen]
> regard to this?
> Paul
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
access[vbcol=seagreen]
because[vbcol=seagreen]
GB.
>

How much memory can 32-bit SQL Server 2000 use on Windows Server 2003 Standard x64 Edition

I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
I have is how much can it address on Win2003 Standard x64? The full 32 GB?
Or does the x64 editions not support the AWE method that the 32-bit version
uses?
Thanks!
PaulThis is a multi-part message in MIME format.
--070906010403080101090103
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
You've mixed up SQL & Windows versions & editions in your question a
little but I think I understand what you're getting at.
You'd be wanting to run the 64 bit edition of SQL Server 2000
(Enterprise) if you're planning on running it on a x64 version of
Windows. Given that, max memory is not really a consideration anymore
because 64 bit addressing works differently to 32 bit addressing and the
64 bit edition of SQL Server 2000 (Enterprise) can address up to 512GB
of memory (no AWE needed anymore); 64-bit addressing has a theoretical
limit of 18 Exabytes. So it's pretty much a case of how much memory can
the OS present to SQL Server?
Advantages of 64 bit SQL Server:
http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Paul Widner wrote:
>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
>Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
>I have is how much can it address on Win2003 Standard x64? The full 32 GB?
>Or does the x64 editions not support the AWE method that the 32-bit version
>uses?
>
>Thanks!
>Paul
>
>
--070906010403080101090103
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>You've mixed up SQL & Windows versions & editions in your
question a little but I think I understand what you're getting at.<br>
<br>
You'd be wanting to run the 64 bit edition of SQL Server 2000
(Enterprise) if you're planning on running it on a x64 version of
Windows. Given that, max memory is not really a consideration anymore
because 64 bit addressing works differently to 32 bit addressing and
the 64 bit edition of SQL Server 2000 (Enterprise) can address up to
512GB of memory (no AWE needed anymore); 64-bit addressing has a
theoretical limit of 18 Exabytes. So it's pretty much a case of how
much memory can the OS present to SQL Server?<br>
<br>
Advantages of 64 bit SQL Server:<br>
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp</a><br>">http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp">http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp</a><br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Paul Widner wrote:
<blockquote cite="midu0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl" type="cite">
<pre wrap="">I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
I have is how much can it address on Win2003 Standard x64? The full 32 GB?
Or does the x64 editions not support the AWE method that the 32-bit version
uses?
Thanks!
Paul
</pre>
</blockquote>
</body>
</html>
--070906010403080101090103--|||Mike,
I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is for Itanium. For x64,
you need to run 32 bit SQL server (which requires sp4 of SQL2K to be supported).
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:Obp8hhkcFHA.220@.TK2MSFTNGP12.phx.gbl...
> You've mixed up SQL & Windows versions & editions in your question a
> little but I think I understand what you're getting at.
> You'd be wanting to run the 64 bit edition of SQL Server 2000
> (Enterprise) if you're planning on running it on a x64 version of
> Windows. Given that, max memory is not really a consideration anymore
> because 64 bit addressing works differently to 32 bit addressing and the
> 64 bit edition of SQL Server 2000 (Enterprise) can address up to 512GB
> of memory (no AWE needed anymore); 64-bit addressing has a theoretical
> limit of 18 Exabytes. So it's pretty much a case of how much memory can
> the OS present to SQL Server?
> Advantages of 64 bit SQL Server:
> http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
>
> Paul Widner wrote:
>>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
>>Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
>>I have is how much can it address on Win2003 Standard x64? The full 32 GB?
>>Or does the x64 editions not support the AWE method that the 32-bit version
>>uses?
>>
>>Thanks!
>>Paul
>>
>>
>|||This is a multi-part message in MIME format.
--070805020306060307040909
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
On SQL matters I am much more likely to be wrong than you Tibor.
After conducting a little research on the matter I see you are quite
right (http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx). I
eat humble pie.
Oh well, at least I found that out before going out and buying SQL
64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
SQL strategy methinks (good excuse to get some Itanium boxes <grin>).
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Tibor Karaszi wrote:
>Mike,
>I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is for Itanium. For x64,
>you need to run 32 bit SQL server (which requires sp4 of SQL2K to be supported).
>
>
--070805020306060307040909
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>On SQL matters I am much more likely to be wrong than you Tibor.<br>
<br>
After conducting a little research on the matter I see you are quite
right (</tt><tt><a class="moz-txt-link-freetext" href="http://links.10026.com/?link=http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx</a></tt><tt>). ">http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx">http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx</a></tt><tt>).
I eat humble pie.<br>
<br>
Oh well, at least I found that out before going out and buying SQL
64-bit & a brand new quad-Xeon (with EM64T extensions) box running
Win 2003 x64 and </tt><tt>expecting it to run</tt><tt>. Hmmm...I'd
better rethink our 64-bit SQL strategy methinks (good excuse to get
some Itanium boxes <grin>).<br>
</tt>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Tibor Karaszi wrote:
<blockquote cite="mid%23FTpD4lcFHA.3040@.TK2MSFTNGP14.phx.gbl"
type="cite">
<pre wrap="">Mike,
I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is for Itanium. For x64,
you need to run 32 bit SQL server (which requires sp4 of SQL2K to be supported).
</pre>
</blockquote>
</body>
</html>
--070805020306060307040909--|||Thanks for the confirmation, Mike. I also found below at the sp4 home page (which you probably seen,
but just in case):
"SQL Server 2000 Service Pack 4 (SP4) adds platform support for Microsoft Windows Server 2003 x64
Edition, allowing 32-bit SQL Server 2000 applications to run on 64-bit platforms using the Windows
on Windows emulator (WOW64). SP4 addresses specific issues discovered in SQL Server 2000 since its
ship date. SP4 is also the first service pack to service the 64-bit edition of SQL Server."
http://www.microsoft.com/sql/downloads/2000/sp4.mspx
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin>).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
>
> Tibor Karaszi wrote:
>>Mike,
>>I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is for Itanium. For x64,
>>you need to run 32 bit SQL server (which requires sp4 of SQL2K to be supported).
>>
>|||I'm guessing here but I think SQL2000 Enterprise should be able to access up
to 4GB on W2003 x64.
A 32bit app won't be able to access any more than 4GB on W2003 x64 because
you can't use PAE extensions, but I think as SQL 2000 is compiled to be
large memory aware it will be able to access more than 2GB.
Peter Lawton
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
>question I have is how much can it address on Win2003 Standard x64? The
>full 32 GB? Or does the x64 editions not support the AWE method that the
>32-bit version uses?
>
> Thanks!
> Paul
>|||PMJI, but SQL2005 will run 64-bit on Windows x64, so I wouldn't rush out and
spend money on an Itanium system unless you really need the performance.
It's supposed to be released the week of Nov. 7th.
Mike Kruchten
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/productinfo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin>).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> Tibor Karaszi wrote:
>>Mike,
>>I might be wrong, but as I understand it, the only 64 bit SQL server 2000
>>is for Itanium. For x64,
>>you need to run 32 bit SQL server (which requires sp4 of SQL2K to be
>>supported).
>>
>|||Anyone know how I can go about getting an offical response from Microsoft in
regard to this?
Paul
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
> I'm guessing here but I think SQL2000 Enterprise should be able to access
> up to 4GB on W2003 x64.
> A 32bit app won't be able to access any more than 4GB on W2003 x64 because
> you can't use PAE extensions, but I think as SQL 2000 is compiled to be
> large memory aware it will be able to access more than 2GB.
> Peter Lawton
> "Paul Widner" <paul_widner@.hotmail.com> wrote in message
> news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
>>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
>>question I have is how much can it address on Win2003 Standard x64? The
>>full 32 GB? Or does the x64 editions not support the AWE method that the
>>32-bit version uses?
>>
>> Thanks!
>> Paul
>|||This is a multi-part message in MIME format.
--050007030501090103020505
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Flick Paul Flessner or Euan Garden an email?
--
*mike hodgson* |/ database administrator/ | mallesons stephen jaques
*T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
*E* mailto:mike.hodgson@.mallesons.nospam.com |* W* http://www.mallesons.com
Paul Widner wrote:
>Anyone know how I can go about getting an offical response from Microsoft in
>regard to this?
>Paul
>
>"Peter Lawton" <devnull@.dummydomain.com> wrote in message
>news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
>
>>I'm guessing here but I think SQL2000 Enterprise should be able to access
>>up to 4GB on W2003 x64.
>>A 32bit app won't be able to access any more than 4GB on W2003 x64 because
>>you can't use PAE extensions, but I think as SQL 2000 is compiled to be
>>large memory aware it will be able to access more than 2GB.
>>Peter Lawton
>>"Paul Widner" <paul_widner@.hotmail.com> wrote in message
>>news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>>
>>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
>>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
>>question I have is how much can it address on Win2003 Standard x64? The
>>full 32 GB? Or does the x64 editions not support the AWE method that the
>>32-bit version uses?
>>
>>Thanks!
>>Paul
>>
>>
>
>
--050007030501090103020505
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
<tt>Flick Paul Flessner or Euan Garden an email?</tt><br>
<div class="moz-signature">
<title></title>
<meta http-equiv="Content-Type" content="text/html; ">
<p><span lang="en-au"><font face="Tahoma" size="2">--<br>
</font> </span><b><span lang="en-au"><font face="Tahoma" size="2">mike
hodgson</font></span></b><span lang="en-au"> <font face="Tahoma"
size="2">|</font><i><font face="Tahoma"> </font><font face="Tahoma"
size="2"> database administrator</font></i><font face="Tahoma" size="2">
| mallesons</font><font face="Tahoma"> </font><font face="Tahoma"
size="2">stephen</font><font face="Tahoma"> </font><font face="Tahoma"
size="2"> jaques</font><font face="Tahoma"><br>
</font><b><font face="Tahoma" size="2">T</font></b><font face="Tahoma"
size="2"> +61 (2) 9296 3668 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2"> F</font></b><font face="Tahoma" size="2"> +61
(2) 9296 3885 |</font><b><font face="Tahoma"> </font><font
face="Tahoma" size="2">M</font></b><font face="Tahoma" size="2"> +61
(408) 675 907</font><br>
<b><font face="Tahoma" size="2">E</font></b><font face="Tahoma" size="2">
<a href="http://links.10026.com/?link=mailto:mike.hodgson@.mallesons.nospam.com">
mailto:mike.hodgson@.mallesons.nospam.com</a> |</font><b><font
face="Tahoma"> </font><font face="Tahoma" size="2">W</font></b><font
face="Tahoma" size="2"> <a href="http://links.10026.com/?link=/">http://www.mallesons.com">
http://www.mallesons.com</a></font></span> </p>
</div>
<br>
<br>
Paul Widner wrote:
<blockquote cite="midO1fHdVpcFHA.1384@.TK2MSFTNGP09.phx.gbl" type="cite">
<pre wrap="">Anyone know how I can go about getting an offical response from Microsoft in
regard to this?
Paul
"Peter Lawton" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:devnull@.dummydomain.com"><devnull@.dummydomain.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl">news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I'm guessing here but I think SQL2000 Enterprise should be able to access
up to 4GB on W2003 x64.
A 32bit app won't be able to access any more than 4GB on W2003 x64 because
you can't use PAE extensions, but I think as SQL 2000 is compiled to be
large memory aware it will be able to access more than 2GB.
Peter Lawton
"Paul Widner" <a class="moz-txt-link-rfc2396E" href="http://links.10026.com/?link=mailto:paul_widner@.hotmail.com"><paul_widner@.hotmail.com></a> wrote in message
<a class="moz-txt-link-freetext" href="http://links.10026.com/?link=news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl">news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl</a>...
</pre>
<blockquote type="cite">
<pre wrap="">I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
question I have is how much can it address on Win2003 Standard x64? The
full 32 GB? Or does the x64 editions not support the AWE method that the
32-bit version uses?
Thanks!
Paul
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap=""><!-->
</pre>
</blockquote>
</body>
</html>
--050007030501090103020505--|||Did anyone ever get an answer to this?
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:O1fHdVpcFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Anyone know how I can go about getting an offical response from Microsoft
in
> regard to this?
> Paul
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
> > I'm guessing here but I think SQL2000 Enterprise should be able to
access
> > up to 4GB on W2003 x64.
> >
> > A 32bit app won't be able to access any more than 4GB on W2003 x64
because
> > you can't use PAE extensions, but I think as SQL 2000 is compiled to be
> > large memory aware it will be able to access more than 2GB.
> >
> > Peter Lawton
> >
> > "Paul Widner" <paul_widner@.hotmail.com> wrote in message
> > news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
> >>I know the maximum memory that Server 2003 Standard x64 supports is 32
GB.
> >>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
> >>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
> >>question I have is how much can it address on Win2003 Standard x64? The
> >>full 32 GB? Or does the x64 editions not support the AWE method that the
> >>32-bit version uses?
> >>
> >>
> >> Thanks!
> >> Paul
> >>
> >
> >
>

How much memory can 32-bit SQL Server 2000 use on Windows Server 2003 Standard x64 Edi

I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k Adv.
Server and 64 GB on Win2k Datacenter with AWE enabled. The grand question
I have is how much can it address on Win2003 Standard x64? The full 32 GB?
Or does the x64 editions not support the AWE method that the 32-bit version
uses?
Thanks!
PaulMike,
I might be wrong, but as I understand it, the only 64 bit SQL server 2000 is
for Itanium. For x64,
you need to run 32 bit SQL server (which requires sp4 of SQL2K to be support
ed).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:Obp8hhkcFHA.220@.TK2MSFTNGP12.phx.gbl...
> You've mixed up SQL & Windows versions & editions in your question a
> little but I think I understand what you're getting at.
> You'd be wanting to run the 64 bit edition of SQL Server 2000
> (Enterprise) if you're planning on running it on a x64 version of
> Windows. Given that, max memory is not really a consideration anymore
> because 64 bit addressing works differently to 32 bit addressing and the
> 64 bit edition of SQL Server 2000 (Enterprise) can address up to 512GB
> of memory (no AWE needed anymore); 64-bit addressing has a theoretical
> limit of 18 Exabytes. So it's pretty much a case of how much memory can
> the OS present to SQL Server?
> Advantages of 64 bit SQL Server:
> http://www.microsoft.com/sql/64bit/...tAdvantages.asp
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* [url]http://www.mallesons.com[/url
]
>
> Paul Widner wrote:
>
>|||Thanks for the confirmation, Mike. I also found below at the sp4 home page (
which you probably seen,
but just in case):
"SQL Server 2000 Service Pack 4 (SP4) adds platform support for Microsoft Wi
ndows Server 2003 x64
Edition, allowing 32-bit SQL Server 2000 applications to run on 64-bit platf
orms using the Windows
on Windows emulator (WOW64). SP4 addresses specific issues discovered in SQL
Server 2000 since its
ship date. SP4 is also the first service pack to service the 64-bit edition
of SQL Server."
http://www.microsoft.com/sql/downloads/2000/sp4.mspx
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/...nfo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin> ).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W* [url]http://www.mallesons.com[/url
]
>
> Tibor Karaszi wrote:
>
>|||I'm guessing here but I think SQL2000 Enterprise should be able to access up
to 4GB on W2003 x64.
A 32bit app won't be able to access any more than 4GB on W2003 x64 because
you can't use PAE extensions, but I think as SQL 2000 is compiled to be
large memory aware it will be able to access more than 2GB.
Peter Lawton
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>I know the maximum memory that Server 2003 Standard x64 supports is 32 GB.
>I know that 32-bit SQL Server 2003 Enterprise can address 8 GB on Win2k
>Adv. Server and 64 GB on Win2k Datacenter with AWE enabled. The grand
>question I have is how much can it address on Win2003 Standard x64? The
>full 32 GB? Or does the x64 editions not support the AWE method that the
>32-bit version uses?
>
> Thanks!
> Paul
>|||PMJI, but SQL2005 will run 64-bit on Windows x64, so I wouldn't rush out and
spend money on an Itanium system unless you really need the performance.
It's supposed to be released the week of Nov. 7th.
Mike Kruchten
"Mike Hodgson" <mike.hodgson@.mallesons.nospam.com> wrote in message
news:uBu$aXmcFHA.1044@.TK2MSFTNGP10.phx.gbl...
> On SQL matters I am much more likely to be wrong than you Tibor.
> After conducting a little research on the matter I see you are quite
> right (http://www.microsoft.com/sql/64bit/...nfo/sysreq.mspx). I
> eat humble pie.
> Oh well, at least I found that out before going out and buying SQL
> 64-bit & a brand new quad-Xeon (with EM64T extensions) box running Win
> 2003 x64 and expecting it to run. Hmmm...I'd better rethink our 64-bit
> SQL strategy methinks (good excuse to get some Itanium boxes <grin> ).
> --
> *mike hodgson* |/ database administrator/ | mallesons stephen jaques
> *T* +61 (2) 9296 3668 |* F* +61 (2) 9296 3885 |* M* +61 (408) 675 907
> *E* mailto:mike.hodgson@.mallesons.nospam.com |* W*
> http://www.mallesons.com
>
> Tibor Karaszi wrote:
>
>|||Anyone know how I can go about getting an offical response from Microsoft in
regard to this?
Paul
"Peter Lawton" <devnull@.dummydomain.com> wrote in message
news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
> I'm guessing here but I think SQL2000 Enterprise should be able to access
> up to 4GB on W2003 x64.
> A 32bit app won't be able to access any more than 4GB on W2003 x64 because
> you can't use PAE extensions, but I think as SQL 2000 is compiled to be
> large memory aware it will be able to access more than 2GB.
> Peter Lawton
> "Paul Widner" <paul_widner@.hotmail.com> wrote in message
> news:u0vkGadcFHA.2520@.TK2MSFTNGP09.phx.gbl...
>|||Did anyone ever get an answer to this?
"Paul Widner" <paul_widner@.hotmail.com> wrote in message
news:O1fHdVpcFHA.1384@.TK2MSFTNGP09.phx.gbl...
> Anyone know how I can go about getting an offical response from Microsoft
in
> regard to this?
> Paul
>
> "Peter Lawton" <devnull@.dummydomain.com> wrote in message
> news:O1t0yJncFHA.2520@.TK2MSFTNGP09.phx.gbl...
access[vbcol=seagreen]
because[vbcol=seagreen]
GB.[vbcol=seagreen]
>sql

Friday, March 23, 2012

How many SQL 7.0 instances can you install on windows 2000 cluster

Hi,
How many SQL 7.0 instances can you install on windows 2000 cluster?
windows 2000 cluster supports a maximum of 4 nodes.
Regards,
AD
Hi
SQL Server 7.0 only supports 2 nodes in a cluster in an Active/Active
configuration.
If I were you, I would use SQL 2000 clustering. SQL 7.0 clustering was hard
to install and maintain.
Regards
Mike
"AD" wrote:

> Hi,
> How many SQL 7.0 instances can you install on windows 2000 cluster?
> windows 2000 cluster supports a maximum of 4 nodes.
>
> Regards,
> AD

Monday, March 19, 2012

How many connections does MSDE support?

I always thought that MSDE supported up to 5 concurrent connections. However, I was just at Microsoft's Web site and it says that MSDE supports *25* concurrent connections:

http://www.microsoft.com/sql/msde/downloads/download.asp

There's a big difference between 5 connections and 25. Did MS just release a new version of MSDE? Is there a catch?Read carefully:

Basic websites that serve up to 25 concurrent users.

That means exactly that: In most cases, they expect that 25 concurrent users will be OK with the 5 concurrent OPERATIONS allowed, since a WEb application does not dedicate a connection to each user, and the web application will not be doing an operation for each user all the time.|||Hi Douglas, I have your book. :)

So, MS is assuming that 1 out of 5 Web users will have a database operation running? That's a pretty lofting assumption. So, if MS assumed that 1 out of every 10 Web users has a database operation running, then they could have said it serves up to 50 Web users?|||Hope you like the book! It makes a great Stocking Stuffer <g>.

As for the estimate of the number of users, it is just that. Your code might hit the database hard enough that you can only support 10 concurrent users, or you might be able to get 40.

Here is a link to a document that explains the Workload Governor.

how many connection sqlexpress supports

I see this question a lot, so I thought I would go ahead and post the answer here.

Q: How many connections does SQL Server Express support?

A: Unlike MSDE, SQL Server Express does not limit connections. SQL Server Express supports:

1 gb RAM (note the machine can have more memory, but 1gb will be used by SQL Express) 1 processor (again, the machine can have more, but just 1 proc will be used by SQL Express) 4 gb database size (note, there can be multiple databases, but none of them individually can be more than 4 gb)

Hope this helps,

Thanks< MJ

Is it right that only 5 database users can connect to SQL Server express 2005 engine at the same time?

How many concurrent users with SQL Server 2000 Standard & 2GB ?

Standard costs 2000 euros approx (5CALs)
Enterprise costs 40000 euros apprx

Standard only supports 2GB or RAM
How many concurrent users do you think standard edtion can handle in a Dual Xeon 2.8 with 2GB ram ?

Enterprise is very expensive. sucks that standard can't handle more than 2GB Ram::How many concurrent users do you think standard edtion can handle in a Dual Xeon 2.8
::with 2GB ram ?

Neither I nor anyone else can answer this.

See, from CONNECTED users, you talk possibly about 30.000 or so - users do need very little.

But when you talk about users DOING something, then it totally depends on how expensive the QUERIES are. This can be 1, can be 10, can be 1000. Noone can answer this qwuery in the generic way you ask it.