Showing posts with label access. Show all posts
Showing posts with label access. 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
>
>
|||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...
>
|||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
>
>|||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...
>|||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...
>
>

Monday, March 26, 2012

Max Connections?

Hi,
We're frequently getting a 'Timeout Expired' error on ASP pages that access
one of our SQL database servers. Is there a limit to the number of
concurrent connections with SQL server 2000 or has anyone else experienced
this behaviour? It is becoming quite frequent (around once a day). The only
thing that seems to solve it is a restart of the SQL services.
Thanks for any assistance - Ian"Ian Bell" <ianbell6862@.hotmail.comm> wrote in
news:uva#C1vSFHA.3392@.TK2MSFTNGP12.phx.gbl:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that
> access one of our SQL database servers. Is there a limit to the number
> of concurrent connections with SQL server 2000 or has anyone else
> experienced this behaviour? It is becoming quite frequent (around once
> a day). The only thing that seems to solve it is a restart of the SQL
> services.
> Thanks for any assistance - Ian
>
See FAQ for limited connections in IIS. Review your ASP code.
http://www.microsoft.com/technet/community/columns/insider/iisi1203.mspx#EB
AA
--
Regards
JTC ^..^|||According to this article there is not a limit to the number of concurrent
connections with SQL server databases
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>|||According to this article there is not a limit to concurrent connections in
SQL Server 2000.
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/architec/8_ar_sa2_0ciq.asp
You might want to check the setting for multiple connections in your website
settings in IIS.
"Ian Bell" wrote:
> Hi,
> We're frequently getting a 'Timeout Expired' error on ASP pages that access
> one of our SQL database servers. Is there a limit to the number of
> concurrent connections with SQL server 2000 or has anyone else experienced
> this behaviour? It is becoming quite frequent (around once a day). The only
> thing that seems to solve it is a restart of the SQL services.
> Thanks for any assistance - Ian
>
>sql

Monday, March 19, 2012

matrix or crosstab query

Hi friends,

I need to write a crosstab query in oracle like we do in Access. Here are my sample tables.

tblCat
---
sno (primary key)
cat_id

tblDistribution
------
area_id
dist_id (primary key)
dist_name

tblConsumer
-----
serviceno (primary key)
sno (references sno(tblCat))
area_id

I need the display as follows:

categories
----
dist_id & dist_name 1 2 3 4 5 ... (cat_ids...)
-------------------
id, name concatenated count(serviceno).....

ie., I want the No.of service for each category Id and for dist_id and dist_name.... The cat_id should not be duplicated.

Plz help me out of thios query as I need it badly. I've done it using crosstab query wizard in Access. here is the query

TRANSFORM Count(tb_consumer.Service_No) AS CountOfService_No
SELECT tb_distribution.Dist_Id + " - " +tb_distribution.Dist_Name AS Id_Name
FROM (tb_category INNER JOIN tb_consumer ON tb_category.SNO = tb_consumer.SNO) INNER JOIN tb_distribution ON tb_consumer.Area_Id = tb_distribution.Area_Id
GROUP BY tb_distribution.Dist_Id, tb_distribution.Dist_Name
PIVOT tb_category.Cat_Id;

If any one can, plz tell me how to write or convert the same to ORACLE or SQL Server.

Thanks in advance...!The process is very simple.

You need to create a pivot table :

field1 will appear as row header
field2 will appear as column header

Select field1, field2 into pivot from mytable where ....

This gives you a table with all the data you need to work with.

Now ...

Select field1, count(field2) as totalfield2,
sum(case field2 when 'xxxx' then 1 else 0) as colhdr1,
sum(case field2 when 'yyyy' then 1 else 0) as colhdr2,
sum(case field3 when 'zzzz' then 1 else 0) as colhdr3
from pivot
group by field1
order by field1

This should produce the results much like the Access CrossTab query. You can refine it to meet your requirements. I did not fully understand what you were looking for, but hopefully this will help.

you need to recreate the pivot table every time you run!

Friday, March 9, 2012

Matrix and ReportItems

1. Using ReportItems, what items within a matrix is accessible?
2. Can ReportItems be used in one matrix to access textboxes in another
matrix?hi Deb,
unfortunally i've seen nobody to answer at your question. i have the same
problem: wanted to use reportItems in the matrix cells. since now i haven't
succed. i solved the problem by calculating what i needed in other datasets
and call the values like parameters. the problem is that the report makes a
lifetime for deploying and that's not very nice.
if you found a better solution please write it.
regards, Mirela
"Deb" wrote:
> 1. Using ReportItems, what items within a matrix is accessible?
> 2. Can ReportItems be used in one matrix to access textboxes in another
> matrix?

Wednesday, March 7, 2012

Materials Needed

As I am seeing SQL is t-o-t-a-l-l-y different from Access.
Is it practical to use VBA, or does that not apply?
Does anyone have some great links or book references on learning SQL.
Hungry for Info
David WYes, it is.
Which version of SQL are you using? Things change between versions,
especially in the administrative tools area.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David W" <davidw@.mcintoshconstruction.net> wrote in message
news:eo7OYGwQGHA.196@.TK2MSFTNGP10.phx.gbl...
> As I am seeing SQL is t-o-t-a-l-l-y different from Access.
> Is it practical to use VBA, or does that not apply?
> Does anyone have some great links or book references on learning SQL.
> Hungry for Info
> David W
>|||SQL Server Version 8.00.194
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23Q47INwQGHA.1160@.TK2MSFTNGP09.phx.gbl...
> Yes, it is.
> Which version of SQL are you using? Things change between versions,
> especially in the administrative tools area.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
> "David W" <davidw@.mcintoshconstruction.net> wrote in message
> news:eo7OYGwQGHA.196@.TK2MSFTNGP10.phx.gbl...
>|||>> As I am seeing SQL is t-o-t-a-l-l-y different from Access.Is it practical
to use VBA, or does that not apply? <<
Does not apply; VB is a proprietary programming language and SQL is a
ANSI/ISO Standard database language.
I like my books, but Rick van der Lans has a good intro and if you read
French, Fredericx Berouard's book is great and a bit more current.|||What do you mean by "materials" and what do you mean by "use VBA"?
The MSDE 2000 or SSEE 2005 editions of SQL Server are available for free
download. There is also a version of It can even be used in a production
environment, if you consider the CPU, memory, database size, and licensing
limitations:
http://msdn.microsoft.com/vstudio/e...ql/default.aspx
SSEE 2005 Documentation and Samples:
http://www.microsoft.com/downloads/...&displaylang=en
The SQL Server Management Studio application does not come bundled with SSEE
2005, but it can be downloaded from here:
http://www.microsoft.com/downloads/...&displaylang=en
Using SSEE from Visual Basic 6:
http://msdn.microsoft.com/vbrun/vbf...singsqlexpress/
As far as leaning SQL; it's like learning French. I can't really point to
any comprehensive site on the web, and it would involve perhaps a year or
more of job related mentoring or perhaps taking some CIS classes.
"David W" <davidw@.mcintoshconstruction.net> wrote in message
news:eo7OYGwQGHA.196@.TK2MSFTNGP10.phx.gbl...
> As I am seeing SQL is t-o-t-a-l-l-y different from Access.
> Is it practical to use VBA, or does that not apply?
> Does anyone have some great links or book references on learning SQL.
> Hungry for Info
> David W
>|||That is the RTM version of SQL 2000. I suggest downloading SQL Service Pack
4. There are some major security fixes that you need to add.
http://www.microsoft.com/downloads/...&displaylang=en
While you are there, you can get the updated Books-On-Line:
http://www.microsoft.com/sql/prodin...ions/books.mspx
For SQL Server administration, "Inside SQL Server 2000" by Kalen Delaney is
the first book you should own. There are lots of other books that drill
deeper into specific administrative areas, but this is the best "total
picture" book out there.
Joe Celko does have a good SQL programming book, "SQL For Smarties". He has
a strong preference for ANSI standard SQL over Microsoft T-SQL but the book
still has a lot of good information for Microsoft SQL users.
If you are just starting out with SQL Server, you might want to look at SQL
Server 2005 instead of SQL Server 2000 as your learning platform.
VBA is a scripting language for applications. SQL is a database service,
which is an altogether different beast. You will use T-SQL scripts and SQL
administrative tools to manage the system. You will need to write your own
front-end application for user data presentation and interaction. Here is
the most valuable advice I can give you on that subject. Do not, no matter
how tempting it is, use Access as your SQL front end. Repeat, Do not use
Access as a SQL Server front-end application.
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David W" <davidw@.mcintoshconstruction.net> wrote in message
news:OXDnS53QGHA.6008@.TK2MSFTNGP10.phx.gbl...
> SQL Server Version 8.00.194
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23Q47INwQGHA.1160@.TK2MSFTNGP09.phx.gbl...
>|||What are your thought about SQL Server Express?
We will only have 5 pcs sharing this database.
Is there limitation with Express, I could not find anything about
limits,liscences,etc.
"Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
news:%23yeKIv6QGHA.4792@.TK2MSFTNGP14.phx.gbl...
> That is the RTM version of SQL 2000. I suggest downloading SQL Service
> Pack 4. There are some major security fixes that you need to add.
> http://www.microsoft.com/downloads/...&displaylang=en
> While you are there, you can get the updated Books-On-Line:
> http://www.microsoft.com/sql/prodin...ions/books.mspx
> For SQL Server administration, "Inside SQL Server 2000" by Kalen Delaney
> is the first book you should own. There are lots of other books that
> drill deeper into specific administrative areas, but this is the best
> "total picture" book out there.
> Joe Celko does have a good SQL programming book, "SQL For Smarties". He
> has a strong preference for ANSI standard SQL over Microsoft T-SQL but the
> book still has a lot of good information for Microsoft SQL users.
> If you are just starting out with SQL Server, you might want to look at
> SQL Server 2005 instead of SQL Server 2000 as your learning platform.
> VBA is a scripting language for applications. SQL is a database service,
> which is an altogether different beast. You will use T-SQL scripts and
> SQL administrative tools to manage the system. You will need to write
> your own front-end application for user data presentation and interaction.
> Here is the most valuable advice I can give you on that subject. Do not,
> no matter how tempting it is, use Access as your SQL front end. Repeat,
> Do not use Access as a SQL Server front-end application.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVP
>
>
> "David W" <davidw@.mcintoshconstruction.net> wrote in message
> news:OXDnS53QGHA.6008@.TK2MSFTNGP10.phx.gbl...
>|||SQL Server Express is a good tool for embedded or small scale databases. It
is free, it has some performance and size restrictions and is a lot better
than MSDE, the comparable edition for SQL 2000. If your needs are within
these limitations, it is an excellent product. I would obtain a developer
edition of SQL 2005 for development purposes and deploy to Express.
Here is the product page for SQL Server 2005 Express Edition:
http://www.microsoft.com/sql/editio...ss/default.mspx
Geoff N. Hiten
Senior Database Administrator
Microsoft SQL Server MVP
"David W" <davidw@.mcintoshconstruction.net> wrote in message
news:uEMDUAGRGHA.1160@.TK2MSFTNGP09.phx.gbl...
> What are your thought about SQL Server Express?
> We will only have 5 pcs sharing this database.
> Is there limitation with Express, I could not find anything about
> limits,liscences,etc.
>
> "Geoff N. Hiten" <SQLCraftsman@.gmail.com> wrote in message
> news:%23yeKIv6QGHA.4792@.TK2MSFTNGP14.phx.gbl...
>