Hi,
I have one server with OS Windows 2003 Enterprise edition, SQL Server
2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
Currently i am faceing performance issue. I want to know that this
issue is due to low RAM or due to any other factor.
Should i increase the RAM.
Is there any matrix of Memory Required for SQL Server based on Database
size.
Please give me reply.
Thanks & Regards,
Sajid C.Hi
Does the OS have 512 MB RAM? Are you serious?
<csajid@.gmail.com> wrote in message
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||It has very little to do with the database size and more to do with the
queries that you run.
As you probably realize 512M is way too little, I would say that if this is
a dedicated SQL Server you should have at least 2G, if you run other thing
son the server (IIS, Exchange, ...) you should have 3G or more.
But it all depends, there is no magical limit, the more memory the better
for performance, however more than 4G is more or less pointless on 32 bit
systems (although there are somewhat buggy ways to exceed the limit).
KL.
<csajid@.gmail.com> skrev i meddelandet
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||Hi All,
Thanks U All for ur reply.
Thanks & Regards,
Sajid C.
KL wrote:[vbcol=seagreen]
> It has very little to do with the database size and more to do with the
> queries that you run.
> As you probably realize 512M is way too little, I would say that if this i
s
> a dedicated SQL Server you should have at least 2G, if you run other thing
> son the server (IIS, Exchange, ...) you should have 3G or more.
> But it all depends, there is no magical limit, the more memory the better
> for performance, however more than 4G is more or less pointless on 32 bit
> systems (although there are somewhat buggy ways to exceed the limit).
> KL.
>
> <csajid@.gmail.com> skrev i meddelandet
> news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
Showing posts with label enterprise. Show all posts
Showing posts with label enterprise. Show all posts
Monday, March 26, 2012
How much RAM Required for 2.5 GB of SQL Server 2000 EE database.
Hi,
I have one server with OS Windows 2003 Enterprise edition, SQL Server
2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
Currently i am faceing performance issue. I want to know that this
issue is due to low RAM or due to any other factor.
Should i increase the RAM.
Is there any matrix of Memory Required for SQL Server based on Database
size.
Please give me reply.
Thanks & Regards,
Sajid C.Hi
Does the OS have 512 MB RAM? Are you serious?
<csajid@.gmail.com> wrote in message
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||It has very little to do with the database size and more to do with the
queries that you run.
As you probably realize 512M is way too little, I would say that if this is
a dedicated SQL Server you should have at least 2G, if you run other thing
son the server (IIS, Exchange, ...) you should have 3G or more.
But it all depends, there is no magical limit, the more memory the better
for performance, however more than 4G is more or less pointless on 32 bit
systems (although there are somewhat buggy ways to exceed the limit).
KL.
<csajid@.gmail.com> skrev i meddelandet
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||Hi All,
Thanks U All for ur reply.
Thanks & Regards,
Sajid C.
KL wrote:
> It has very little to do with the database size and more to do with the
> queries that you run.
> As you probably realize 512M is way too little, I would say that if this is
> a dedicated SQL Server you should have at least 2G, if you run other thing
> son the server (IIS, Exchange, ...) you should have 3G or more.
> But it all depends, there is no magical limit, the more memory the better
> for performance, however more than 4G is more or less pointless on 32 bit
> systems (although there are somewhat buggy ways to exceed the limit).
> KL.
>
> <csajid@.gmail.com> skrev i meddelandet
> news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> > Hi,
> >
> > I have one server with OS Windows 2003 Enterprise edition, SQL Server
> > 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> >
> > Currently i am faceing performance issue. I want to know that this
> > issue is due to low RAM or due to any other factor.
> >
> > Should i increase the RAM.
> >
> > Is there any matrix of Memory Required for SQL Server based on Database
> > size.
> >
> >
> > Please give me reply.
> >
> > Thanks & Regards,
> > Sajid C.
> >
I have one server with OS Windows 2003 Enterprise edition, SQL Server
2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
Currently i am faceing performance issue. I want to know that this
issue is due to low RAM or due to any other factor.
Should i increase the RAM.
Is there any matrix of Memory Required for SQL Server based on Database
size.
Please give me reply.
Thanks & Regards,
Sajid C.Hi
Does the OS have 512 MB RAM? Are you serious?
<csajid@.gmail.com> wrote in message
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||It has very little to do with the database size and more to do with the
queries that you run.
As you probably realize 512M is way too little, I would say that if this is
a dedicated SQL Server you should have at least 2G, if you run other thing
son the server (IIS, Exchange, ...) you should have 3G or more.
But it all depends, there is no magical limit, the more memory the better
for performance, however more than 4G is more or less pointless on 32 bit
systems (although there are somewhat buggy ways to exceed the limit).
KL.
<csajid@.gmail.com> skrev i meddelandet
news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> Hi,
> I have one server with OS Windows 2003 Enterprise edition, SQL Server
> 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> Currently i am faceing performance issue. I want to know that this
> issue is due to low RAM or due to any other factor.
> Should i increase the RAM.
> Is there any matrix of Memory Required for SQL Server based on Database
> size.
>
> Please give me reply.
> Thanks & Regards,
> Sajid C.
>|||Hi All,
Thanks U All for ur reply.
Thanks & Regards,
Sajid C.
KL wrote:
> It has very little to do with the database size and more to do with the
> queries that you run.
> As you probably realize 512M is way too little, I would say that if this is
> a dedicated SQL Server you should have at least 2G, if you run other thing
> son the server (IIS, Exchange, ...) you should have 3G or more.
> But it all depends, there is no magical limit, the more memory the better
> for performance, however more than 4G is more or less pointless on 32 bit
> systems (although there are somewhat buggy ways to exceed the limit).
> KL.
>
> <csajid@.gmail.com> skrev i meddelandet
> news:1156245366.871169.255540@.m79g2000cwm.googlegroups.com...
> > Hi,
> >
> > I have one server with OS Windows 2003 Enterprise edition, SQL Server
> > 2000 Enterprise Edition and 512 MB RAM. The database size is 2.5 GB.
> >
> > Currently i am faceing performance issue. I want to know that this
> > issue is due to low RAM or due to any other factor.
> >
> > Should i increase the RAM.
> >
> > Is there any matrix of Memory Required for SQL Server based on Database
> > size.
> >
> >
> > Please give me reply.
> >
> > Thanks & Regards,
> > Sajid C.
> >
How much memory can SQL Enterprise use?
Hi,
I've heard that SQL Enterprise can use up to 4gigs of RAM. Windows 2000
Server can address up to 4gigs of RAM in a single process, but since 2gigs
of that address space is "reserved" -- this means that SQL Server Enterprise
can really only use a maximum 1.7 to 2 gigs of RAM in the SQL Server process
when running on Win2000... My question is: If I install Windows 2003 and
stick SQL Enterprise on that machine, how much memory will SQL be able to
use (in a given process). MSFT's site says that Win2003 can make use of 4
gigs of memory, but will I run into the same problem that Win2000 has in so
far as the first 2gigs of the process' virtual memory space is "reserved"?
Thanks.
DavidSQL Server under W2K Advanced server can use up to 8 GB of
RAM. Under W2K Datacenter it is 32 GB. With W2K3
Enterprise Edition it's 32 GB for 32-bit, 64-bit is 64 GB.
(And so on ...)
To use the advanced memory under 32-bit, you need to use
the /PAE switch and turn AWE on in SQL Server. However,
the memory is not dynamic - it is a fixed static amount.
Under 64-bit, all memory is dynamic.
If you need > 2 GB for SQL but not more then 3 GB, you do
not have to enable /PAE or AWE, but just set /3GB in the
OS, and SQL Server can use up to 3 GB with no problem.
These are the ways you get SQL Server to recognize more
than 2 GB of memory.
>--Original Message--
>Hi,
> I've heard that SQL Enterprise can use up to 4gigs of
RAM. Windows 2000
>Server can address up to 4gigs of RAM in a single
process, but since 2gigs
>of that address space is "reserved" -- this means that
SQL Server Enterprise
>can really only use a maximum 1.7 to 2 gigs of RAM in the
SQL Server process
>when running on Win2000... My question is: If I install
Windows 2003 and
>stick SQL Enterprise on that machine, how much memory
will SQL be able to
>use (in a given process). MSFT's site says that Win2003
can make use of 4
>gigs of memory, but will I run into the same problem that
Win2000 has in so
>far as the first 2gigs of the process' virtual memory
space is "reserved"?
>Thanks.
>David
>
>.
>|||Thanks for the information. I've done a bit of research regarding the
PAE and 3GB switches that you've mentioned and I have a few followup
questions/comments:
- First of all, it appears that these switches aren't available in the
standard version of W2K Server. The Advanced version (or greater) is
required. Is there a smooth upgrade path from standard W2K Server to
Advanced? In other words, can I just install advanced on top of my current
W2K Server, or must I format the drive and do a clean installed of Advanced?
- /PAE is an OS-specific switch, not SQL-specific. Setting this switch
means that the OS can address more than 4 gigs of physical memory. Is this
correct?
- /3G is an OS-specific switch. Setting this switch means that a given
process can access a maximum of 3 gigs of memory as opposed to the standard
2 gigs of memory. Could you please elaborate on this switch? It seems
partially redundant to /PAE. If I've switched on /PAE, why would I want /3G?
- AWE isn't a switch, but an API that can be used by individual
applications such as SQL Server. SQL Server uses AWE to address memory
beyond 4gigs. The memory is reserved for exclusive access by the AWE client
(in my case, SQL Server). Is this correct?
So for a machine that has 6 gigs of RAM:
- I *do* need the /PAE switch because the OS needs to address beyond 4
gigs of RAM.
- I *do* need SQL Server to run in AWE mode because it needs to access
to more than 4 gigs of RAM.
- Do I need /3gb?
Thanks for the clarification...
David
"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
news:09c201c3a9a8$97307100$a301280a@.phx.gbl...
> SQL Server under W2K Advanced server can use up to 8 GB of
> RAM. Under W2K Datacenter it is 32 GB. With W2K3
> Enterprise Edition it's 32 GB for 32-bit, 64-bit is 64 GB.
> (And so on ...)
> To use the advanced memory under 32-bit, you need to use
> the /PAE switch and turn AWE on in SQL Server. However,
> the memory is not dynamic - it is a fixed static amount.
> Under 64-bit, all memory is dynamic.
> If you need > 2 GB for SQL but not more then 3 GB, you do
> not have to enable /PAE or AWE, but just set /3GB in the
> OS, and SQL Server can use up to 3 GB with no problem.
> These are the ways you get SQL Server to recognize more
> than 2 GB of memory.
> >--Original Message--
> >Hi,
> >
> > I've heard that SQL Enterprise can use up to 4gigs of
> RAM. Windows 2000
> >Server can address up to 4gigs of RAM in a single
> process, but since 2gigs
> >of that address space is "reserved" -- this means that
> SQL Server Enterprise
> >can really only use a maximum 1.7 to 2 gigs of RAM in the
> SQL Server process
> >when running on Win2000... My question is: If I install
> Windows 2003 and
> >stick SQL Enterprise on that machine, how much memory
> will SQL be able to
> >use (in a given process). MSFT's site says that Win2003
> can make use of 4
> >gigs of memory, but will I run into the same problem that
> Win2000 has in so
> >far as the first 2gigs of the process' virtual memory
> space is "reserved"?
> >Thanks.
> >
> >David
> >
> >
> >.
> >
I've heard that SQL Enterprise can use up to 4gigs of RAM. Windows 2000
Server can address up to 4gigs of RAM in a single process, but since 2gigs
of that address space is "reserved" -- this means that SQL Server Enterprise
can really only use a maximum 1.7 to 2 gigs of RAM in the SQL Server process
when running on Win2000... My question is: If I install Windows 2003 and
stick SQL Enterprise on that machine, how much memory will SQL be able to
use (in a given process). MSFT's site says that Win2003 can make use of 4
gigs of memory, but will I run into the same problem that Win2000 has in so
far as the first 2gigs of the process' virtual memory space is "reserved"?
Thanks.
DavidSQL Server under W2K Advanced server can use up to 8 GB of
RAM. Under W2K Datacenter it is 32 GB. With W2K3
Enterprise Edition it's 32 GB for 32-bit, 64-bit is 64 GB.
(And so on ...)
To use the advanced memory under 32-bit, you need to use
the /PAE switch and turn AWE on in SQL Server. However,
the memory is not dynamic - it is a fixed static amount.
Under 64-bit, all memory is dynamic.
If you need > 2 GB for SQL but not more then 3 GB, you do
not have to enable /PAE or AWE, but just set /3GB in the
OS, and SQL Server can use up to 3 GB with no problem.
These are the ways you get SQL Server to recognize more
than 2 GB of memory.
>--Original Message--
>Hi,
> I've heard that SQL Enterprise can use up to 4gigs of
RAM. Windows 2000
>Server can address up to 4gigs of RAM in a single
process, but since 2gigs
>of that address space is "reserved" -- this means that
SQL Server Enterprise
>can really only use a maximum 1.7 to 2 gigs of RAM in the
SQL Server process
>when running on Win2000... My question is: If I install
Windows 2003 and
>stick SQL Enterprise on that machine, how much memory
will SQL be able to
>use (in a given process). MSFT's site says that Win2003
can make use of 4
>gigs of memory, but will I run into the same problem that
Win2000 has in so
>far as the first 2gigs of the process' virtual memory
space is "reserved"?
>Thanks.
>David
>
>.
>|||Thanks for the information. I've done a bit of research regarding the
PAE and 3GB switches that you've mentioned and I have a few followup
questions/comments:
- First of all, it appears that these switches aren't available in the
standard version of W2K Server. The Advanced version (or greater) is
required. Is there a smooth upgrade path from standard W2K Server to
Advanced? In other words, can I just install advanced on top of my current
W2K Server, or must I format the drive and do a clean installed of Advanced?
- /PAE is an OS-specific switch, not SQL-specific. Setting this switch
means that the OS can address more than 4 gigs of physical memory. Is this
correct?
- /3G is an OS-specific switch. Setting this switch means that a given
process can access a maximum of 3 gigs of memory as opposed to the standard
2 gigs of memory. Could you please elaborate on this switch? It seems
partially redundant to /PAE. If I've switched on /PAE, why would I want /3G?
- AWE isn't a switch, but an API that can be used by individual
applications such as SQL Server. SQL Server uses AWE to address memory
beyond 4gigs. The memory is reserved for exclusive access by the AWE client
(in my case, SQL Server). Is this correct?
So for a machine that has 6 gigs of RAM:
- I *do* need the /PAE switch because the OS needs to address beyond 4
gigs of RAM.
- I *do* need SQL Server to run in AWE mode because it needs to access
to more than 4 gigs of RAM.
- Do I need /3gb?
Thanks for the clarification...
David
"Allan Hirt" <allanh@.NOSPAMavanade.com> wrote in message
news:09c201c3a9a8$97307100$a301280a@.phx.gbl...
> SQL Server under W2K Advanced server can use up to 8 GB of
> RAM. Under W2K Datacenter it is 32 GB. With W2K3
> Enterprise Edition it's 32 GB for 32-bit, 64-bit is 64 GB.
> (And so on ...)
> To use the advanced memory under 32-bit, you need to use
> the /PAE switch and turn AWE on in SQL Server. However,
> the memory is not dynamic - it is a fixed static amount.
> Under 64-bit, all memory is dynamic.
> If you need > 2 GB for SQL but not more then 3 GB, you do
> not have to enable /PAE or AWE, but just set /3GB in the
> OS, and SQL Server can use up to 3 GB with no problem.
> These are the ways you get SQL Server to recognize more
> than 2 GB of memory.
> >--Original Message--
> >Hi,
> >
> > I've heard that SQL Enterprise can use up to 4gigs of
> RAM. Windows 2000
> >Server can address up to 4gigs of RAM in a single
> process, but since 2gigs
> >of that address space is "reserved" -- this means that
> SQL Server Enterprise
> >can really only use a maximum 1.7 to 2 gigs of RAM in the
> SQL Server process
> >when running on Win2000... My question is: If I install
> Windows 2003 and
> >stick SQL Enterprise on that machine, how much memory
> will SQL be able to
> >use (in a given process). MSFT's site says that Win2003
> can make use of 4
> >gigs of memory, but will I run into the same problem that
> Win2000 has in so
> >far as the first 2gigs of the process' virtual memory
> space is "reserved"?
> >Thanks.
> >
> >David
> >
> >
> >.
> >
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.
>
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
> >>
> >
> >
>
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
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 ways to design data warehouse?
I knew that there are 4 ways to design data warehouse
which are enterprise data warehouse,dependent data mart,
independent data mart and federated warehouse but i want
to know that which job is suitable to each way?I would recommend you start here -
http://www.ralphkimball.com/html/articles.html
Ray Higdon MCSE, MCDBA, CCNA
--
"goofy" <anonymous@.discussions.microsoft.com> wrote in message
news:42b301c3fea0$bbb29010$a301280a@.phx.gbl...
> I knew that there are 4 ways to design data warehouse
> which are enterprise data warehouse,dependent data mart,
> independent data mart and federated warehouse but i want
> to know that which job is suitable to each way?
which are enterprise data warehouse,dependent data mart,
independent data mart and federated warehouse but i want
to know that which job is suitable to each way?I would recommend you start here -
http://www.ralphkimball.com/html/articles.html
Ray Higdon MCSE, MCDBA, CCNA
--
"goofy" <anonymous@.discussions.microsoft.com> wrote in message
news:42b301c3fea0$bbb29010$a301280a@.phx.gbl...
> I knew that there are 4 ways to design data warehouse
> which are enterprise data warehouse,dependent data mart,
> independent data mart and federated warehouse but i want
> to know that which job is suitable to each way?
Labels:
database,
dependent,
design,
enterprise,
federated,
independent,
mart,
microsoft,
mysql,
oracle,
server,
sql,
warehouse,
warehousewhich
how many times a DML was executed ?
how can I find out , how many times a SQL statment was executed ?
can it be done using enterprise Manager , T-sql scripts ?
(same as V$sql.EXECUTIONS in oracle)
10x in advanceLook in Books-On-Line at system table syscacheobjects and column usecounts. I believe that once the object is swapped out of cache and brought back in the count will be initiated to zero.
Example script
SELECT SUBSTRING(master..syscacheobjects.sql,1,35) AS SQL,
master..syscacheobjects.cacheobjtype AS CacheObjectType,
master..syscacheobjects.objtype AS ObjectType,
SUBSTRING(master..sysdatabases.name,1,25) AS DatabaseName,
master..syscacheobjects.pagesused,
master..syscacheobjects.usecounts AS [Number of times used since inception],
master..syscacheobjects.sqlbytes AS [Length of name or batch submitted (in bytes)],
SUBSTRING(master..sysusers.name,1,15) AS Creator
From master..syscacheobjects
INNER JOIN
master..sysdatabases
ON master..syscacheobjects.dbid = master..sysdatabases.dbid
INNER JOIN
master..sysusers
ON master..syscacheobjects.uid = master..sysusers.uid
ORDER BY
master..sysdatabases.name
can it be done using enterprise Manager , T-sql scripts ?
(same as V$sql.EXECUTIONS in oracle)
10x in advanceLook in Books-On-Line at system table syscacheobjects and column usecounts. I believe that once the object is swapped out of cache and brought back in the count will be initiated to zero.
Example script
SELECT SUBSTRING(master..syscacheobjects.sql,1,35) AS SQL,
master..syscacheobjects.cacheobjtype AS CacheObjectType,
master..syscacheobjects.objtype AS ObjectType,
SUBSTRING(master..sysdatabases.name,1,25) AS DatabaseName,
master..syscacheobjects.pagesused,
master..syscacheobjects.usecounts AS [Number of times used since inception],
master..syscacheobjects.sqlbytes AS [Length of name or batch submitted (in bytes)],
SUBSTRING(master..sysusers.name,1,15) AS Creator
From master..syscacheobjects
INNER JOIN
master..sysdatabases
ON master..syscacheobjects.dbid = master..sysdatabases.dbid
INNER JOIN
master..sysusers
ON master..syscacheobjects.uid = master..sysusers.uid
ORDER BY
master..sysdatabases.name
Monday, March 19, 2012
How many Enterprise Licenses to Buy?
We are building up a clustered server configuration with two nodes. Each
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.
How many instances are you going to run in the cluster? You license per active instances (unless you
will run several instances in the same node, i.e., the other node doesn't do any SQL Server
processing at all). And, if you license per processor, you need to multiply with the number of
processor sockets you use in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflicting
> information on this. Thanks for any info.
|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.
|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me a
link? That sounds like what we need. Do I then need CALs for each user?
|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>
|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though the
device CALs option is much better suited for our situation.
|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?
|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.
How many instances are you going to run in the cluster? You license per active instances (unless you
will run several instances in the same node, i.e., the other node doesn't do any SQL Server
processing at all). And, if you license per processor, you need to multiply with the number of
processor sockets you use in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflicting
> information on this. Thanks for any info.
|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.
|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me a
link? That sounds like what we need. Do I then need CALs for each user?
|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>
|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though the
device CALs option is much better suited for our situation.
|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?
|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
How many Enterprise Licenses to Buy?
We are building up a clustered server configuration with two nodes. Each
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.How many instances are you going to run in the cluster? You license per active instances (unless you
will run several instances in the same node, i.e., the other node doesn't do any SQL Server
processing at all). And, if you license per processor, you need to multiply with the number of
processor sockets you use in the machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflicting
> information on this. Thanks for any info.|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me a
link? That sounds like what we need. Do I then need CALs for each user?|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though the
device CALs option is much better suited for our situation.|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.How many instances are you going to run in the cluster? You license per active instances (unless you
will run several instances in the same node, i.e., the other node doesn't do any SQL Server
processing at all). And, if you license per processor, you need to multiply with the number of
processor sockets you use in the machine.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflicting
> information on this. Thanks for any info.|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me a
link? That sounds like what we need. Do I then need CALs for each user?|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though the
device CALs option is much better suited for our situation.|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
--
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
Labels:
building,
clustered,
configuration,
database,
enterprise,
licenses,
microsoft,
ml580,
mysql,
node,
nodes,
oracle,
processors,
server,
sql
How many Enterprise Licenses to Buy?
We are building up a clustered server configuration with two nodes. Each
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.How many instances are you going to run in the cluster? You license per acti
ve instances (unless you
will run several instances in the same node, i.e., the other node doesn't do
any SQL Server
processing at all). And, if you license per processor, you need to multiply
with the number of
processor sockets you use in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we ne
ed
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflictin
g
> information on this. Thanks for any info.|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me
a
link? That sounds like what we need. Do I then need CALs for each user?|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though th
e
device CALs option is much better suited for our situation.|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
node will be an HP ML580 or DL 580 with 4 processors per server. Do we need
to buy two Enterprise licenses (one for each 4-processor server) or 8
licenses (one for each processor on each server)? I am getting conflicting
information on this. Thanks for any info.How many instances are you going to run in the cluster? You license per acti
ve instances (unless you
will run several instances in the same node, i.e., the other node doesn't do
any SQL Server
processing at all). And, if you license per processor, you need to multiply
with the number of
processor sockets you use in the machine.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we ne
ed
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting conflictin
g
> information on this. Thanks for any info.|||It depends.
First, check with your local Microsoft office. Make sure you have a person
knowledgable about SQL licensing in a clustered environment.
Here is the base page with links to the licensing information:
http://www.microsoft.com/sql/howtobuy/default.mspx#EEAA
Here is the FAQ page
http://www.microsoft.com/sql/howtobuy/faq.mspx
The relevant question and answer are here:
Q. How does licensing work for computers that run SQL Server 2005 in
failover scenarios?
A. Failover support, where servers are clustered together and set to
pick up processing duties if one computer should fail, is now available in
Workgroup, Standard, and Enterprise editions of SQL Server 2005. Under each
of these editions, keeping a passive server for failover purposes does not
require a license as long as the passive server has the same or fewer
processors than the active server (under the per processor scenario). For
details on which failover methods are available under each edition, visit
the SQL Server 2005 Features Comparison page.
Finally, SQL 2005 supports failover clustering on Standard Edition with up
to four processors on each host. If you do not need any other Enterprise
Edition features, you will save a considerable amount of money on licensing
by using Standare Edition. Oh, and look at the DL/ML 585 series wutl
Dual-Core processors. IMHO, the best bang for the bucks.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:3A9EC00F-834F-4F8C-AAB7-041A2354B95D@.microsoft.com...
> We are building up a clustered server configuration with two nodes. Each
> node will be an HP ML580 or DL 580 with 4 processors per server. Do we
> need
> to buy two Enterprise licenses (one for each 4-processor server) or 8
> licenses (one for each processor on each server)? I am getting
> conflicting
> information on this. Thanks for any info.|||We will not be doing any processing on the non-active server. From the MS
web link posted by Tibor (thank you), it looks like we need only the Server
Plus Device CALs model. There will be no web access and I know exactly how
many users will get to it at all times. I had trouble finding where it says
we don't need a license for the passive failover option. Could you send me
a
link? That sounds like what we need. Do I then need CALs for each user?|||Search for "failover" in the FAQ page.
As for the licensing, since you don't have any internet access to the
server, choose whichever licensing model (per-processor or CAL) is cheaper.
That is why Microsoft has multiple licensing models.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:BB370D4D-88FB-4ACC-B8E1-A82932038125@.microsoft.com...
> We will not be doing any processing on the non-active server. From the MS
> web link posted by Tibor (thank you), it looks like we need only the
> Server
> Plus Device CALs model. There will be no web access and I know exactly
> how
> many users will get to it at all times. I had trouble finding where it
> says
> we don't need a license for the passive failover option. Could you send
> me a
> link? That sounds like what we need. Do I then need CALs for each user?
>|||Thank you. BTW, I did find the FAQ site on licensing. Thanks very much for
your help. I don't think our software supplier is asking us the right
questions, as they went straight for the per-processor option even though th
e
device CALs option is much better suited for our situation.|||If I already have device CALS for existing SQL servers, do I need to buy new
ones for a new SQL server I am installing or do I just buy the server
license? It looks like the device CAL is good for connections to any number
of different servers, so long as each server has a license.
When doing that install on a new server, do I have to tell it how many CALs
I bought or is it basically the honor system?
I have seen some folks wondering how to enter the number of CALs. If I add
more CALs, do I need to tell my instance of SQL server how many I added?|||A Device CAL can connect to any number of SQL servers.
There is no technical enforcement measure for CAL enforcement built into SQL
Server. It is a good idea to set up a licensing server and funnel CAL
configuration through that so you have a single point of maintenance.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:DF76E12F-B60D-48B2-BFB6-5A4364B46F95@.microsoft.com...
> If I already have device CALS for existing SQL servers, do I need to buy
> new
> ones for a new SQL server I am installing or do I just buy the server
> license? It looks like the device CAL is good for connections to any
> number
> of different servers, so long as each server has a license.
> When doing that install on a new server, do I have to tell it how many
> CALs
> I bought or is it basically the honor system?
> I have seen some folks wondering how to enter the number of CALs. If I
> add
> more CALs, do I need to tell my instance of SQL server how many I added?
How many concurrent users with SQL Server 2000 Standard & 2GB ?
Standard costs 2000 euros approx (5CALs)
Enterprise costs 40000 euros apprx
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.
Monday, March 12, 2012
How long should a backup take ?
Backups suddenly went from about 20 minutes to 2 hours. W2K Server, 6gb, 4 1.9 P4 processors, SQL 2000 Enterprise Edition, SAN, 52 gb database. Backup is during off hours with little contention.Where are the backups going? Is it a network drive or a local array? You
should also check to be sure there isn't a failed drive in the array.
--
Andrew J. Kelly SQL MVP
"Cincy D" <anonymous@.discussions.microsoft.com> wrote in message
news:1FA8C398-37B2-4F66-9AB7-C276562E1363@.microsoft.com...
> Backups suddenly went from about 20 minutes to 2 hours. W2K Server, 6gb, 4
1.9 P4 processors, SQL 2000 Enterprise Edition, SAN, 52 gb database. Backup
is during off hours with little contention.|||It is going to a SAN.|||You should have the SAN people run diagnostics to ensure its running OK.
You might want to check to be sure they didn't reconfigure the SAN about
that same time. Can you copy a file of that size to the same location with
better results? There isn't much to a full backup that would cause slow
downs other than bandwith issues.
--
Andrew J. Kelly SQL MVP
"Cincy D" <anonymous@.discussions.microsoft.com> wrote in message
news:D81E8EB5-7677-49F4-A281-D9BF3C42552A@.microsoft.com...
> It is going to a SAN.
should also check to be sure there isn't a failed drive in the array.
--
Andrew J. Kelly SQL MVP
"Cincy D" <anonymous@.discussions.microsoft.com> wrote in message
news:1FA8C398-37B2-4F66-9AB7-C276562E1363@.microsoft.com...
> Backups suddenly went from about 20 minutes to 2 hours. W2K Server, 6gb, 4
1.9 P4 processors, SQL 2000 Enterprise Edition, SAN, 52 gb database. Backup
is during off hours with little contention.|||It is going to a SAN.|||You should have the SAN people run diagnostics to ensure its running OK.
You might want to check to be sure they didn't reconfigure the SAN about
that same time. Can you copy a file of that size to the same location with
better results? There isn't much to a full backup that would cause slow
downs other than bandwith issues.
--
Andrew J. Kelly SQL MVP
"Cincy D" <anonymous@.discussions.microsoft.com> wrote in message
news:D81E8EB5-7677-49F4-A281-D9BF3C42552A@.microsoft.com...
> It is going to a SAN.
Friday, February 24, 2012
How I can register MSSQL Server 2000 by IP Address
How I can register MSSQL Server 2000 by IP Address-
I installed MSSQL Server 2000 sp3a, Enterprise edition on windows 2000 advanced server box with sp4. Its primarily give instance with name like servername/sqlindia, Where sqlindia is instance and servername is physical machine name.
I would like to registration of sqlserver instance by IP Address. How I can do it.
Thanking You
R.MallEnsure the client network utility is mentioned with ALIAS using IP Address.
I installed MSSQL Server 2000 sp3a, Enterprise edition on windows 2000 advanced server box with sp4. Its primarily give instance with name like servername/sqlindia, Where sqlindia is instance and servername is physical machine name.
I would like to registration of sqlserver instance by IP Address. How I can do it.
Thanking You
R.MallEnsure the client network utility is mentioned with ALIAS using IP Address.
how i can make script Database with Data?
hi
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||Try www.sqlscripter.com to generate data scripts. It's free.
"Tark Siala" wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise
+
> SP4.
> i have database contains Tables, and i want make script to build Tables on
> other Database,
> but i need this script include Data in Tables too, i can make that ? and
> how?
> thanks
> --
> Tarek M. Siala
>
>
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply|||Try www.sqlscripter.com to generate data scripts. It's free.
"Tark Siala" wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise
+
> SP4.
> i have database contains Tables, and i want make script to build Tables on
> other Database,
> but i need this script include Data in Tables too, i can make that ? and
> how?
> thanks
> --
> Tarek M. Siala
>
>
how i can make script Database with Data?
hi
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
how i can make script Database with Data?
hi
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
how i can make script Database with Data?
hi
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
i am working on Windows 2000 Advanced Server + SP4 and SQL2000 Enterprise +
SP4.
i have database contains Tables, and i want make script to build Tables on
other Database,
but i need this script include Data in Tables too, i can make that ? and
how?
thanks
--
Tarek M. Sialahi,
Tark Siala wrote:
> hi
> i am working on Windows 2000 Advanced Server + SP4 and SQL2000
> Enterprise + SP4.
> i have database contains Tables, and i want make script to build
> Tables on other Database,
> but i need this script include Data in Tables too, i can make that ?
> and how?
> thanks
you can have a look at a free prj of mine, at the link following my sign.,
DbaMgr2k, which include an "INSERT INTO" script generation feature at table
level...
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.bizhttp://italy.mvps.org
DbaMgr2k ver 0.19.0 - DbaMgr ver 0.63.0 and further SQL Tools
-- remove DMO to reply
Subscribe to:
Posts (Atom)