master sysmessages: bit

Showing posts with label bit. Show all posts

Friday, March 30, 2012

Max memory on 32/64 bit

I'm tired of Googling for a definitive answer

What is the max memory SQL Server can access in this setup:
SQL 2000, Enterprise edition, 32 bit
Windows 2003, EE, 64 bit
I'm thinking 32GB from what I've read, but I want to make sure before I tell
my customer what to buy...
Thanks!
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
These should provide the definitive answer you seek.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
> I'm tired of Googling for a definitive answer

> What is the max memory SQL Server can access in this setup:
> SQL 2000, Enterprise edition, 32 bit
> Windows 2003, EE, 64 bit
> I'm thinking 32GB from what I've read, but I want to make sure before I
> tell my customer what to buy...
> Thanks!
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>
|||A leetle confused here:
with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
Seems like the first option there is missing something...
Second option is not relevant to my 32 bit SQL scenario, but good info
nonetheless...
Thanks
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
> With no boot ini settings 2 Gigs.
> With /3Gig boot ini 3 Gigs
> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>
|||Thanks Arnie, but the BOL link does not specifically reference Windows 2003
EE, 64 bit (or any other Win2K3 versions...)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
> These should provide the definitive answer you seek.
> Configuration -Maximum Capacity Specifications
> 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> 2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
> 2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>
|||That doesn't read well - try this
With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
Note that the procedure cache and other caches will still see IIRC 2 Gigs
and most of the OS memory will be used with the 64 address windowing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>A leetle confused here:
> with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
> 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
> Seems like the first option there is missing something...
> Second option is not relevant to my 32 bit SQL scenario, but good info
> nonetheless...
> Thanks
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
>
|||Oops, sorry Kevin, this is a better source for you.
http://www.support.microsoft.com/?id=283037
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e2a1oSlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
> Thanks Arnie, but the BOL link does not specifically reference Windows
> 2003 EE, 64 bit (or any other Win2K3 versions...)
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
>
|||Thanks for the clarification

Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OX3SnVlEHHA.3768@.TK2MSFTNGP06.phx.gbl...
> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>
|||But 64-bit Windows does not support PAE.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
Linchi
"Hilary Cotter" wrote:

> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>
>

Max memory on 32/64 bit

I'm tired of Googling for a definitive answer :)
What is the max memory SQL Server can access in this setup:
SQL 2000, Enterprise edition, 32 bit
Windows 2003, EE, 64 bit
I'm thinking 32GB from what I've read, but I want to make sure before I tell
my customer what to buy...
Thanks!
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.comThese should provide the definitive answer you seek.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
> I'm tired of Googling for a definitive answer :)
> What is the max memory SQL Server can access in this setup:
> SQL 2000, Enterprise edition, 32 bit
> Windows 2003, EE, 64 bit
> I'm thinking 32GB from what I've read, but I want to make sure before I
> tell my customer what to buy...
> Thanks!
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>|||With no boot ini settings 2 Gigs.
With /3Gig boot ini 3 Gigs
With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32 Gigs
with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit. 64
bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
> I'm tired of Googling for a definitive answer :)
> What is the max memory SQL Server can access in this setup:
> SQL 2000, Enterprise edition, 32 bit
> Windows 2003, EE, 64 bit
> I'm thinking 32GB from what I've read, but I want to make sure before I
> tell my customer what to buy...
> Thanks!
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>|||A leetle confused here:
with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
Seems like the first option there is missing something...
Second option is not relevant to my 32 bit SQL scenario, but good info
nonetheless...
Thanks
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
> With no boot ini settings 2 Gigs.
> With /3Gig boot ini 3 Gigs
> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>> I'm tired of Googling for a definitive answer :)
>> What is the max memory SQL Server can access in this setup:
>> SQL 2000, Enterprise edition, 32 bit
>> Windows 2003, EE, 64 bit
>> I'm thinking 32GB from what I've read, but I want to make sure before I
>> tell my customer what to buy...
>> Thanks!
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>|||Thanks Arnie, but the BOL link does not specifically reference Windows 2003
EE, 64 bit (or any other Win2K3 versions...)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
> These should provide the definitive answer you seek.
> Configuration -Maximum Capacity Specifications
> 2000
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
> 2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
> 2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>> I'm tired of Googling for a definitive answer :)
>> What is the max memory SQL Server can access in this setup:
>> SQL 2000, Enterprise edition, 32 bit
>> Windows 2003, EE, 64 bit
>> I'm thinking 32GB from what I've read, but I want to make sure before I
>> tell my customer what to buy...
>> Thanks!
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>|||That doesn't read well - try this
With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
Note that the procedure cache and other caches will still see IIRC 2 Gigs
and most of the OS memory will be used with the 64 address windowing.
--
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>A leetle confused here:
> with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
> 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
> Seems like the first option there is missing something...
> Second option is not relevant to my 32 bit SQL scenario, but good info
> nonetheless...
> Thanks
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
>> With no boot ini settings 2 Gigs.
>> With /3Gig boot ini 3 Gigs
>> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
>> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
>> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>> I'm tired of Googling for a definitive answer :)
>> What is the max memory SQL Server can access in this setup:
>> SQL 2000, Enterprise edition, 32 bit
>> Windows 2003, EE, 64 bit
>> I'm thinking 32GB from what I've read, but I want to make sure before I
>> tell my customer what to buy...
>> Thanks!
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>>
>|||Oops, sorry Kevin, this is a better source for you.
http://www.support.microsoft.com/?id=283037
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e2a1oSlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
> Thanks Arnie, but the BOL link does not specifically reference Windows
> 2003 EE, 64 bit (or any other Win2K3 versions...)
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
>> These should provide the definitive answer you seek.
>> Configuration -Maximum Capacity Specifications
>> 2000
>> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_ts_8dbn.asp
>> 2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
>> 2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
>>
>> --
>> Arnie Rowland, Ph.D.
>> Westwood Consulting, Inc
>> Most good judgment comes from experience.
>> Most experience comes from bad judgment.
>> - Anonymous
>> You can't help someone get up a hill without getting a little closer to
>> the top yourself.
>> - H. Norman Schwarzkopf
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>> I'm tired of Googling for a definitive answer :)
>> What is the max memory SQL Server can access in this setup:
>> SQL 2000, Enterprise edition, 32 bit
>> Windows 2003, EE, 64 bit
>> I'm thinking 32GB from what I've read, but I want to make sure before I
>> tell my customer what to buy...
>> Thanks!
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>>
>|||Thanks for the clarification :)
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OX3SnVlEHHA.3768@.TK2MSFTNGP06.phx.gbl...
> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>>A leetle confused here:
>> with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
>> 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
>> Seems like the first option there is missing something...
>> Second option is not relevant to my 32 bit SQL scenario, but good info
>> nonetheless...
>> Thanks
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
>> news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
>> With no boot ini settings 2 Gigs.
>> With /3Gig boot ini 3 Gigs
>> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
>> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
>> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
>> --
>> Hilary Cotter
>> Looking for a SQL Server replication book?
>> http://www.nwsu.com/0974973602.html
>> Looking for a FAQ on Indexing Services/SQL FTS
>> http://www.indexserverfaq.com
>>
>> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
>> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>> I'm tired of Googling for a definitive answer :)
>> What is the max memory SQL Server can access in this setup:
>> SQL 2000, Enterprise edition, 32 bit
>> Windows 2003, EE, 64 bit
>> I'm thinking 32GB from what I've read, but I want to make sure before I
>> tell my customer what to buy...
>> Thanks!
>> --
>> Kevin Hill
>> 3NF Consulting
>> http://www.3nf-inc.com/NewsGroups.htm
>> Real-world stuff I run across with SQL Server:
>> http://kevin3nf.blogspot.com
>>
>>
>>
>|||But 64-bit Windows does not support PAE.
http://www.microsoft.com/whdc/system/platform/server/PAE/PAEmem.mspx
Linchi
"Hilary Cotter" wrote:
> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
> >A leetle confused here:
> >
> > with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
> >
> > 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
> >
> > Seems like the first option there is missing something...
> >
> > Second option is not relevant to my 32 bit SQL scenario, but good info
> > nonetheless...
> >
> > Thanks
> > --
> > Kevin Hill
> > 3NF Consulting
> > http://www.3nf-inc.com/NewsGroups.htm
> >
> > Real-world stuff I run across with SQL Server:
> > http://kevin3nf.blogspot.com
> >
> >
> > "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> > news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
> >> With no boot ini settings 2 Gigs.
> >> With /3Gig boot ini 3 Gigs
> >> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
> >> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
> >> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
> >>
> >> --
> >> Hilary Cotter
> >>
> >> Looking for a SQL Server replication book?
> >> http://www.nwsu.com/0974973602.html
> >>
> >> Looking for a FAQ on Indexing Services/SQL FTS
> >> http://www.indexserverfaq.com
> >>
> >>
> >>
> >> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> >> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
> >> I'm tired of Googling for a definitive answer :)
> >>
> >> What is the max memory SQL Server can access in this setup:
> >>
> >> SQL 2000, Enterprise edition, 32 bit
> >> Windows 2003, EE, 64 bit
> >>
> >> I'm thinking 32GB from what I've read, but I want to make sure before I
> >> tell my customer what to buy...
> >>
> >> Thanks!
> >>
> >> --
> >> Kevin Hill
> >> 3NF Consulting
> >> http://www.3nf-inc.com/NewsGroups.htm
> >>
> >> Real-world stuff I run across with SQL Server:
> >> http://kevin3nf.blogspot.com
> >>
> >>
> >>
> >>
> >>
> >
> >
>
>

Max memory on 32/64 bit

I'm tired of Googling for a definitive answer

What is the max memory SQL Server can access in this setup:
SQL 2000, Enterprise edition, 32 bit
Windows 2003, EE, 64 bit
I'm thinking 32GB from what I've read, but I want to make sure before I tell
my customer what to buy...
Thanks!
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.comThese should provide the definitive answer you seek.
Configuration -Maximum Capacity Specifications
2000
http://msdn.microsoft.com/library/d...br />
8dbn.asp
2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
> I'm tired of Googling for a definitive answer

> What is the max memory SQL Server can access in this setup:
> SQL 2000, Enterprise edition, 32 bit
> Windows 2003, EE, 64 bit
> I'm thinking 32GB from what I've read, but I want to make sure before I
> tell my customer what to buy...
> Thanks!
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
>|||A leetle confused here:
with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
Seems like the first option there is missing something...
Second option is not relevant to my 32 bit SQL scenario, but good info
nonetheless...
Thanks
--
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
> With no boot ini settings 2 Gigs.
> With /3Gig boot ini 3 Gigs
> With /AWE and SQL Server 2000 32 bit the data cache can see a max of 32
> Gigs with AWE enabled on SQL Server and PAE enabled on Windows 2003 64
> bit. 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>|||Thanks Arnie, but the BOL link does not specifically reference Windows 2003
EE, 64 bit (or any other Win2K3 versions...)
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Arnie Rowland" <arnie@.1568.com> wrote in message
news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
> These should provide the definitive answer you seek.
> Configuration -Maximum Capacity Specifications
> 2000
> http://msdn.microsoft.com/library/d... />
s_8dbn.asp
> 2005 http://msdn2.microsoft.com/en-us/library/ms143287.aspx
> 2005 http://msdn2.microsoft.com/en-us/library/ms143432.aspx
>
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to
> the top yourself.
> - H. Norman Schwarzkopf
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:OC2SSikEHHA.3524@.TK2MSFTNGP06.phx.gbl...
>|||That doesn't read well - try this
With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
Note that the procedure cache and other caches will still see IIRC 2 Gigs
and most of the OS memory will be used with the 64 address windowing.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>A leetle confused here:
> with AWE enabled on SQL Server and PAE enabled on Windows 2003 64 bit.
> 64 bit SQL 2000 EE can see 64 Gigs on Windows 2003 64 bit
> Seems like the first option there is missing something...
> Second option is not relevant to my 32 bit SQL scenario, but good info
> nonetheless...
> Thanks
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:el$vr3kEHHA.4832@.TK2MSFTNGP06.phx.gbl...
>|||Oops, sorry Kevin, this is a better source for you.
http://www.support.microsoft.com/?id=283037
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
"Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
news:e2a1oSlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
> Thanks Arnie, but the BOL link does not specifically reference Windows
> 2003 EE, 64 bit (or any other Win2K3 versions...)
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Arnie Rowland" <arnie@.1568.com> wrote in message
> news:eaVxm0kEHHA.3520@.TK2MSFTNGP04.phx.gbl...
>|||Thanks for the clarification

Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OX3SnVlEHHA.3768@.TK2MSFTNGP06.phx.gbl...
> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>|||But 64-bit Windows does not support PAE.
http://www.microsoft.com/whdc/syste...PAE/PAEmem.mspx
Linchi
"Hilary Cotter" wrote:

> That doesn't read well - try this
> With SQL Server 2000 EE 32 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 32 Gigs.
> With SQL Server 2000 EE 64 bit with AWE enable running on Windows 2003 64
> bit EE with PAE enabled, the data cache can see a max of 64 Gigs.
> Note that the procedure cache and other caches will still see IIRC 2 Gigs
> and most of the OS memory will be used with the 64 address windowing.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Kevin3NF" <kevin@.SPAMTRAP.3nf-inc.com> wrote in message
> news:us7AISlEHHA.4380@.TK2MSFTNGP04.phx.gbl...
>
>

max memory for SSIS?

If we have a SQL Server 2005 standard edition/Windows 2003 Standard
Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the
maximum size of the memory we could possibly have?
Thank you,
ShivaAnswered in microsoft.public.sqlserver.integrationsvcs
*mike hodgson*
http://sqlnerd.blogspot.com
Shiva wrote:

>If we have a SQL Server 2005 standard edition/Windows 2003 Standard
>Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the
>maximum size of the memory we could possibly have?
>Thank you,
>Shiva
>
>
>

Max memory for SSIS

If we have a SQL Server 2005 standard edition/Windows 2003 Standard Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the maximum size of the memory we could possibly have?

Thank you,

Shiva

SQL 2005 standard doesn't have a maximum memory, you are constrained by your OS and hardware. I think it's around 4 gigs for 2003 standard 32bit.|||

yosonu wrote:

If we have a SQL Server 2005 standard edition/Windows 2003 Standard Environment on a 32 bit 2 dual core proc Dell 2850 server, what is the maximum size of the memory we could possibly have?

Thank you,

Shiva

Is this a question about SSIS? If so, read this: http://blogs.conchango.com/jamiethomson/archive/2005/05/29/1486.aspx

If not, try a different forum.

-Jamie

|||

The 32bit Windows limit is 2GB per process. You can increase this to 3GB, using the boot.ini switch, /3GB.

A classic tip around this is to use several packages and Execute Process Tasks to combine them, but set the out of process option on, as this means each package then gets 2GB as each is it's own process. For small packages this may be detrimental though.

sql

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
Aramid
The MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
AramidThe MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.
4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

max memory

Hi All,
I noticed that SQL 2000 seems to be eating up a bit more memory
(about 100Mb more) than the maximum memory that I have set. Is this a
normal behavior?
Thanks.
AramidThe MAX Memory setting is for the memory pool only and does not take into
account the MemToLeave area. The MemToLeave can take up to 384MB's in
addition to the Max Memory if there is enough to go around.
--
Andrew J. Kelly SQL MVP
"Aramid" <aramid@.hotmail.com> wrote in message
news:44kst11d8pu4g6nhmch70q9la3ngu02jav@.4ax.com...
> Hi All,
> I noticed that SQL 2000 seems to be eating up a bit more memory
> (about 100Mb more) than the maximum memory that I have set. Is this a
> normal behavior?
> Thanks.
> Aramid

Saturday, February 25, 2012

Matching algorithm

I have a db full of names and identifiers. Was wondering if anyone could direct me towards a good dupe eliminating algorithm or bit of logic to look at?
Thanks!What will be your basis for eliminating duplicates ?|||Originally posted by rnealejr
What will be your basis for eliminating duplicates ?

Name dupes and identifiers, some names may be similar, some addresses may be simialr. Each row will have approximately 10 identifiers, but some will be nnull. It is fairly dirty data.|||But how do you determine which rows to delete (like keying off the most recent timestamp) or will it be a visual comparison (so will you need to route these duplicates to a holding table) ?|||Originally posted by rnealejr
But how do you determine which rows to delete (like keying off the most recent timestamp) or will it be a visual comparison (so will you need to route these duplicates to a holding table) ?

Yes I wil need to move them to a holding table. It will be compared visually using all.|||You should post more info about your table of duplicities.
Generic query looks like this

select d1.*
into ClearTable
from DuplTable d1
join
(
select IdCol1,IdCol2,...
from DuplTable d2
group by IdCol1,IdCol2,...
having count(*)=1
) x on (d1.IdCol1=x.IdCol1 or (d1.IdCol1 is null and x.IdCol1 is null))
and (d1.IdCol2=x.IdCol2 or (d1.IdCol2 is null and x.IdCol2 is null))
.
.
.
select d1.*
into HoldingTable
from DuplTable d1
join
(
select IdCol1,IdCol2,...
from DuplTable d2
group by IdCol1,IdCol2,...
having count(*)>1
) x on (d1.IdCol1=x.IdCol1 or (d1.IdCol1 is null and x.IdCol1 is null))
and (d1.IdCol2=x.IdCol2 or (d1.IdCol2 is null and x.IdCol2 is null))
.
.
.
select * from ClearTable
select * from HoldingTable|||Originally posted by ispaleny
You should post more info about your table of duplicities.

Awesome, I am going to try that format. My original table is pretty dirty. It is Lname, fname, SSN, address, city, state, country, phone number, etc., about 5 more identifiers. It is around 3 million records, some complete, some not. Spellings are different in some cases, middle names are there in other cases.

Thanks for your help.
:)

Friday, March 30, 2012

Max memory on 32/64 bit

Max memory on 32/64 bit

Max memory on 32/64 bit

max memory for SSIS?

Max memory for SSIS

max memory

max memory

max memory

Saturday, February 25, 2012

Matching algorithm

master sysmessages

Blog Archive

About Me