MDAC 2.7 Question

Hey Guy's,
I have a Windows 2003 Server (Standard Edition)
It also has SQL Server 2000 with Service Pack 3.
I am using this for testing my companies software compatability with Windows
2003.
Our software installs MDAC to work properly at the moment 2.7, but when our
installer runs it says cannot install as MDAC won't install it only supports
versions of Windows up to 2000...Is there a version available for 2003 yet?
Thanks,
Chris.
-mcpAFAIK, W2K3 comes with MDAC 2.8. This doesn't seem to be available for download (yet). Why not
re-write the install program so it check for MDAC version, if lower than the your supported
level, you give an option to install. If higher than the tested (supported) level, well. In this
case, you quite simply need to test the sw on a machine with MDAC 2.8 (a W2K3 machine).
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Chris" <-@.-.com> wrote in message news:ubRdgKuRDHA.1072@.TK2MSFTNGP10.phx.gbl...
> Hey Guy's,
> I have a Windows 2003 Server (Standard Edition)
> It also has SQL Server 2000 with Service Pack 3.
> I am using this for testing my companies software compatability with Windows
> 2003.
> Our software installs MDAC to work properly at the moment 2.7, but when our
> installer runs it says cannot install as MDAC won't install it only supports
> versions of Windows up to 2000...Is there a version available for 2003 yet?
> Thanks,
> Chris.
> -mcp
>
>|||Can we get the MDAC mappings associated with the SPs of Windows and SQL =Server ? I've been searching for sometime for a site with this =consolidated information ...
-- HTH,
Vinod Kumar
MCSE, DBA, MCAD
SCT Software Solutions http://www32.brinkster.com/sqlvinod
"Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message news:eAOegWuRDHA.1552@.TK2MSFTNGP12.phx.gbl...
> AFAIK, W2K3 comes with MDAC 2.8. This doesn't seem to be available for =download (yet). Why not
> re-write the install program so it check for MDAC version, if lower =than the your supported
> level, you give an option to install. If higher than the tested =(supported) level, well. In this
> case, you quite simply need to test the sw on a machine with MDAC 2.8 =(a W2K3 machine).
> > -- > Tibor Karaszi, SQL Server MVP
> Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> > > "Chris" <-@.-.com> wrote in message =news:ubRdgKuRDHA.1072@.TK2MSFTNGP10.phx.gbl...
> > Hey Guy's,
> >
> > I have a Windows 2003 Server (Standard Edition)
> > It also has SQL Server 2000 with Service Pack 3.
> >
> > I am using this for testing my companies software compatability with =Windows
> > 2003.
> >
> > Our software installs MDAC to work properly at the moment 2.7, but =when our
> > installer runs it says cannot install as MDAC won't install it only =supports
> > versions of Windows up to 2000...Is there a version available for =2003 yet?
> >
> > Thanks,
> >
> > Chris.
> > -mcp
> >
> >
> >
> >|||I haven't searched for such site. Here's what I have checked/remember by heart:
W2K MDAC 2.5
W2K sp1 MDAC 2.5 sp1
W2K sp2 MDAC 2.5 sp2
SQL2K MDAC 2.6
XP MDAC 2.7
W2K3 MDAC 2.8
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Vinodk" <vinodk_sct@.hotmail.com> wrote in message
news:%23YDVQguRDHA.3700@.tk2msftngp13.phx.gbl...
Can we get the MDAC mappings associated with the SPs of Windows and SQL Server ? I've been
searching for sometime for a site with this consolidated information ...
--
HTH,
Vinod Kumar
MCSE, DBA, MCAD
SCT Software Solutions
http://www32.brinkster.com/sqlvinod
"Tibor Karaszi" <tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in message
news:eAOegWuRDHA.1552@.TK2MSFTNGP12.phx.gbl...
> AFAIK, W2K3 comes with MDAC 2.8. This doesn't seem to be available for download (yet). Why not
> re-write the install program so it check for MDAC version, if lower than the your supported
> level, you give an option to install. If higher than the tested (supported) level, well. In
this
> case, you quite simply need to test the sw on a machine with MDAC 2.8 (a W2K3 machine).
> --
> Tibor Karaszi, SQL Server MVP
> Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
>
> "Chris" <-@.-.com> wrote in message news:ubRdgKuRDHA.1072@.TK2MSFTNGP10.phx.gbl...
> > Hey Guy's,
> >
> > I have a Windows 2003 Server (Standard Edition)
> > It also has SQL Server 2000 with Service Pack 3.
> >
> > I am using this for testing my companies software compatability with Windows
> > 2003.
> >
> > Our software installs MDAC to work properly at the moment 2.7, but when our
> > installer runs it says cannot install as MDAC won't install it only supports
> > versions of Windows up to 2000...Is there a version available for 2003 yet?
> >
> > Thanks,
> >
> > Chris.
> > -mcp
> >
> >
> >
>|||Cool Tibor ...
But I think you missed SQL SP3a ?
and thankx in advance ... :) ...
And just a twist to the whole thing is it possible to find the MDAC =version from ISQLW window? I know abt the version ... But this ... Hmmm =... I would be interested in knowing this also ... -- HTH,
Vinod Kumar
MCSE, DBA, MCAD
SCT Software Solutions http://www32.brinkster.com/sqlvinod
"Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message news:OB3mMmuRDHA.2236@.tk2msftngp13.phx.gbl...
> I haven't searched for such site. Here's what I have checked/remember =by heart:
> > W2K MDAC 2.5
> W2K sp1 MDAC 2.5 sp1
> W2K sp2 MDAC 2.5 sp2
> > SQL2K MDAC 2.6
> > XP MDAC 2.7
> W2K3 MDAC 2.8
> -- > Tibor Karaszi, SQL Server MVP
> Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> > > "Vinodk" <vinodk_sct@.hotmail.com> wrote in message
> news:%23YDVQguRDHA.3700@.tk2msftngp13.phx.gbl...
> Can we get the MDAC mappings associated with the SPs of Windows and =SQL Server ? I've been
> searching for sometime for a site with this consolidated information =...
> > -- > HTH,
> Vinod Kumar
> MCSE, DBA, MCAD
> SCT Software Solutions
> http://www32.brinkster.com/sqlvinod
> > > "Tibor Karaszi" =<tibor.please_reply_to_public_forum.karaszi@.cornerstone.se> wrote in =message
> news:eAOegWuRDHA.1552@.TK2MSFTNGP12.phx.gbl...
> > AFAIK, W2K3 comes with MDAC 2.8. This doesn't seem to be available =for download (yet). Why not
> > re-write the install program so it check for MDAC version, if lower =than the your supported
> > level, you give an option to install. If higher than the tested =(supported) level, well. In
> this
> > case, you quite simply need to test the sw on a machine with MDAC =2.8 (a W2K3 machine).
> >
> > -- > > Tibor Karaszi, SQL Server MVP
> > Archive at: =http://groups.google.com/groups?oi=3Ddjq&as_ugroup=3Dmicrosoft.public.sql=
server
> >
> >
> > "Chris" <-@.-.com> wrote in message =news:ubRdgKuRDHA.1072@.TK2MSFTNGP10.phx.gbl...
> > > Hey Guy's,
> > >
> > > I have a Windows 2003 Server (Standard Edition)
> > > It also has SQL Server 2000 with Service Pack 3.
> > >
> > > I am using this for testing my companies software compatability =with Windows
> > > 2003.
> > >
> > > Our software installs MDAC to work properly at the moment 2.7, but =when our
> > > installer runs it says cannot install as MDAC won't install it =only supports
> > > versions of Windows up to 2000...Is there a version available for =2003 yet?
> > >
> > > Thanks,
> > >
> > > Chris.
> > > -mcp
> > >
> > >
> > >
> >
> >
> >|||>> And just a twist to the whole thing is it possible to find the MDAC
version from ISQLW window?
http://www.aspfaq.com/2057 says:
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'|||Thankx Aaron ... :) ...
-- HTH,
Vinod Kumar
MCSE, DBA, MCAD
SCT Software Solutions http://www32.brinkster.com/sqlvinod
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message =news:#F3B$3uRDHA.2228@.tk2msftngp13.phx.gbl...
> >> And just a twist to the whole thing is it possible to find the MDAC
> version from ISQLW window?
> > http://www.aspfaq.com/2057 says:
> > EXEC master..xp_regread
> N'HKEY_LOCAL_MACHINE',
> N'Software\Microsoft\DataAccess',
> N'Version'
> >

Maximum Transactions

Is there a maximum number of transactions that SQL 2000 Standard can
handle at any given time?
Is this configurable?Standard answer: It Depends
It depends upon Hardware (CPU, memory), network traffic, size of the
transactions, database traffic, query plan, what color shoes you wear, etc.
Obviously a 8 CPU/64Gb/3.4Mhz server can handle quite a few more
transactions per second than a 1 CPU/1GB 1.7mhz server.
Now go take a 'common sense' pill. ;-)
--
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"John Bailo" <jabailo@.texeme.com> wrote in message
news:_NmdnSjCQP6-XlrZnZ2dnUVZ_oidnZ2d@.speakeasy.net...
>
> Is there a maximum number of transactions that SQL 2000 Standard can
> handle at any given time?
> Is this configurable?
>|||Arnie Rowland wrote:
> Standard answer: It Depends
> It depends upon Hardware (CPU, memory), network traffic, size of the
> transactions, database traffic, query plan, what color shoes you wear, etc.
> Obviously a 8 CPU/64Gb/3.4Mhz server can handle quite a few more
> transactions per second than a 1 CPU/1GB 1.7mhz server.
> Now go take a 'common sense' pill. ;-)
>
Is there a way to see the current queued transactions?
And estimate room in the queue space for a given server?|||"John Bailo" <jabailo@.texeme.com> wrote in message
news:y-WdnckMabPZaVrZnZ2dnUVZ_uidnZ2d@.speakeasy.net...
> Arnie Rowland wrote:
> > Standard answer: It Depends
> >
> > It depends upon Hardware (CPU, memory), network traffic, size of the
> > transactions, database traffic, query plan, what color shoes you wear,
etc.
> >
> > Obviously a 8 CPU/64Gb/3.4Mhz server can handle quite a few more
> > transactions per second than a 1 CPU/1GB 1.7mhz server.
> >
> > Now go take a 'common sense' pill. ;-)
> >
> Is there a way to see the current queued transactions?
sp_who active will show you active transactions and any blocked ones.
> And estimate room in the queue space for a given server?
Again, not nearly enough info to go on. What are the size of your
transactions.
Lots of small ones vs lots of large ones will make a big difference.

Maximum number of databases on a server

I was wondering if their is a hard limit to the number of databases that can
be attached to a SQL Server 2000 standard install.
Thanks
32,767 databases per instance of SQL Server.
"Ken" <Ken@.discussions.microsoft.com> wrote in message
news:E12B7A3A-E7A0-41BA-B74E-3A60A166D5EA@.microsoft.com...
> I was wondering if their is a hard limit to the number of databases that
can
> be attached to a SQL Server 2000 standard install.
> Thanks
|||thanks
"Hassan" wrote:

> 32,767 databases per instance of SQL Server.
> "Ken" <Ken@.discussions.microsoft.com> wrote in message
> news:E12B7A3A-E7A0-41BA-B74E-3A60A166D5EA@.microsoft.com...
> can
>
>
|||May I know how to check the number of databases installed?
I checked through the Enterprise Manager, under the databases tree, there are:
-Databases
+mySys
+master
+model
+msdb
+Northwind
+pubs
+tempdb
+Sys
Can I say there are total 8 databases ?
Thanks !
"Ken" wrote:
[vbcol=seagreen]
> thanks
> "Hassan" wrote:
|||select count(*) from master.dbo.sysdatabases
That will tell you exactly how many databases are on your SQL instance.
Although I guess the more "Microsoft approved" way would be using their
views & procs (so as to not directly query the system tables) so that would
be:
exec sp_helpdb
Cheers,
Mike
"CS" <CS@.discussions.microsoft.com> wrote in message
news:5F09FFC1-5343-46FF-B87C-B92BCD6E10A9@.microsoft.com...[vbcol=seagreen]
> May I know how to check the number of databases installed?
> I checked through the Enterprise Manager, under the databases tree, there
> are:
> -Databases
> +mySys
> +master
> +model
> +msdb
> +Northwind
> +pubs
> +tempdb
> +Sys
> Can I say there are total 8 databases ?
> Thanks !
> "Ken" wrote:

Maximum memory that SQL 2005 standard can use....

Hi,
We intend to get a new Windows 2003 standard server with 8GB Ram. We will
also be installing SQL 2005 standard on the same system.
We are aware that Windows 2003 standard server supports up to 4GB Ram and
SQL 2005 standard support up to the maximum ram the server has.
Our question is will SQL 2005 standard maximise all the 8GB ram available on
the server even though it is installed on a Windows 2003 standard server
supports only up to 4GB Ram?
Thanks.
Hi
I'm sure it is relevant to SQL Server 2005 too.
http://support.microsoft.com/default...274750&sd=tech
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.
|||On a 32bit Windows standard server you're limited to 3GB application address
space with the /3GB switch in boot.ini
On a 64bit Windows standard server system you're limited to 4GB RAM total
You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
There really isn't any point in putting more than 4GB in a standard server
as it'll never be used
Peter Lawton
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.
|||The x64 version of Windows Server 2003 standard supports 32GB of RAM.
32-bit is 4gb only, so if you are using 32-bit, you will need to get Server
2003 Enterprise. Note that SQL 2005 Standard supports the maximum that the
OS supports, 32-bit or 64-bit.
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.
|||This is not true for the x64 version of Windows Server 2003 Standard. Don't
know about Itanium.
http://support.microsoft.com/KB/888732
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:uEV$ceTMGHA.2828@.TK2MSFTNGP12.phx.gbl...
> On a 32bit Windows standard server you're limited to 3GB application
> address space with the /3GB switch in boot.ini
> On a 64bit Windows standard server system you're limited to 4GB RAM total
> You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
> There really isn't any point in putting more than 4GB in a standard server
> as it'll never be used
> Peter Lawton
> "Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
> news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
>

Maximum memory that SQL 2005 standard can use....

Hi,
We intend to get a new Windows 2003 standard server with 8GB Ram. We will
also be installing SQL 2005 standard on the same system.
We are aware that Windows 2003 standard server supports up to 4GB Ram and
SQL 2005 standard support up to the maximum ram the server has.
Our question is will SQL 2005 standard maximise all the 8GB ram available on
the server even though it is installed on a Windows 2003 standard server
supports only up to 4GB Ram?
Thanks.Hi
I'm sure it is relevant to SQL Server 2005 too.
http://support.microsoft.com/default.aspx?scid=kb;en-us;274750&sd=tech
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||On a 32bit Windows standard server you're limited to 3GB application address
space with the /3GB switch in boot.ini
On a 64bit Windows standard server system you're limited to 4GB RAM total
You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
There really isn't any point in putting more than 4GB in a standard server
as it'll never be used
Peter Lawton
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||The x64 version of Windows Server 2003 standard supports 32GB of RAM.
32-bit is 4gb only, so if you are using 32-bit, you will need to get Server
2003 Enterprise. Note that SQL 2005 Standard supports the maximum that the
OS supports, 32-bit or 64-bit.
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||This is not true for the x64 version of Windows Server 2003 Standard. Don't
know about Itanium.
http://support.microsoft.com/KB/888732
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:uEV$ceTMGHA.2828@.TK2MSFTNGP12.phx.gbl...
> On a 32bit Windows standard server you're limited to 3GB application
> address space with the /3GB switch in boot.ini
> On a 64bit Windows standard server system you're limited to 4GB RAM total
> You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
> There really isn't any point in putting more than 4GB in a standard server
> as it'll never be used
> Peter Lawton
> "Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
> news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
>> Hi,
>> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
>> also be installing SQL 2005 standard on the same system.
>> We are aware that Windows 2003 standard server supports up to 4GB Ram and
>> SQL 2005 standard support up to the maximum ram the server has.
>> Our question is will SQL 2005 standard maximise all the 8GB ram available
>> on
>> the server even though it is installed on a Windows 2003 standard server
>> supports only up to 4GB Ram?
>> Thanks.
>

Maximum memory that SQL 2005 standard can use....

Hi,
We intend to get a new Windows 2003 standard server with 8GB Ram. We will
also be installing SQL 2005 standard on the same system.
We are aware that Windows 2003 standard server supports up to 4GB Ram and
SQL 2005 standard support up to the maximum ram the server has.
Our question is will SQL 2005 standard maximise all the 8GB ram available on
the server even though it is installed on a Windows 2003 standard server
supports only up to 4GB Ram?
Thanks.Hi
I'm sure it is relevant to SQL Server 2005 too.
http://support.microsoft.com/defaul...;274750&sd=tech
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||On a 32bit Windows standard server you're limited to 3GB application address
space with the /3GB switch in boot.ini
On a 64bit Windows standard server system you're limited to 4GB RAM total
You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
There really isn't any point in putting more than 4GB in a standard server
as it'll never be used
Peter Lawton
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||The x64 version of Windows Server 2003 standard supports 32GB of RAM.
32-bit is 4gb only, so if you are using 32-bit, you will need to get Server
2003 Enterprise. Note that SQL 2005 Standard supports the maximum that the
OS supports, 32-bit or 64-bit.
"Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
> Hi,
> We intend to get a new Windows 2003 standard server with 8GB Ram. We will
> also be installing SQL 2005 standard on the same system.
> We are aware that Windows 2003 standard server supports up to 4GB Ram and
> SQL 2005 standard support up to the maximum ram the server has.
> Our question is will SQL 2005 standard maximise all the 8GB ram available
> on
> the server even though it is installed on a Windows 2003 standard server
> supports only up to 4GB Ram?
> Thanks.|||This is not true for the x64 version of Windows Server 2003 Standard. Don't
know about Itanium.
http://support.microsoft.com/KB/888732
"Peter Lawton" <devnull@.fakedomain.com> wrote in message
news:uEV$ceTMGHA.2828@.TK2MSFTNGP12.phx.gbl...
> On a 32bit Windows standard server you're limited to 3GB application
> address space with the /3GB switch in boot.ini
> On a 64bit Windows standard server system you're limited to 4GB RAM total
> You'd need Windows 2003 Enterprise 32 or 64 bit to use all of your 8GB
> There really isn't any point in putting more than 4GB in a standard server
> as it'll never be used
> Peter Lawton
> "Mousehunt" <Mousehunt@.discussions.microsoft.com> wrote in message
> news:D994E07B-2082-4E4A-A1AF-B18CB9C630F4@.microsoft.com...
>

Maximum memory problem

Hello, everyone:

I have SQL Server 2000 Standard Edition running on Windows 2000 Server. There are always memory full alter. I am going to configure that.

I hope a clearation about a concept. In my enviroment, does SQL Server take maximum memroy upto 2GB, no matter if QWE is enabled?

BOL said AWE is available only in the SQL Server 2000 Enterprise and Developer editions. Does it mean AWE cannot be configured on SQL Server 2000 Standard Edition?

Thanks

ZYTIt's suppose to do that

What? You have other things running on the box?|||Hi, Brett:

No other application is running, only sql server. The physical memory is 4GB. There are alerts. The team in considering to add memory. But it is worried new memory is useless because sql server standard version only take 2GB.

It's suppose to do that

What? You have other things running on the box?|||Yes, AWE cannot be used with SQL Server 2000 Standard Edition. It's limited to 2GB of memory.|||Yes, AWE cannot be used with SQL Server 2000 Standard Edition. It's limited to 2GB of memory.

Not only that, but he's running Windows 2000 Standard. OS Limit is 4GB. No benefit to running AWE on that platform.

AWE is used once you get above 4GB RAM. To get >4 GB RAM, you will need:

Windows 2000 Advanced Server (up to 8 GB RAM)
Windows 2000 Datacenter (Can't remember the limit)
Windows 2003 Enterprise (up to 32 GB RAM)
Windows 2003 Datacenter (up to 64 GB RAM)

Or you could go with Windows 2003 x64 and basically ignore your RAM limits.:shocked:

Regards,

hmscott

Maximum Memory and SQL 2005 (Yukon)

I beleive Express has a memory limit of 1GB, but does anyone know what the
Standard Edition memory limit will be when its released? ie Current Std Ed
is 2GB.
Thanks
Mickb>I beleive Express has a memory limit of 1GB, but does anyone know what the
> Standard Edition memory limit will be when its released? ie Current Std Ed
> is 2GB.
I don't believe that this information has been decided, and if it has, I
don't think it is public yet.
A

Max. memory limit for SQL Standard edition.

I read somewhere that the SQL Standard edition can only use the memory up to
2Gb.
Is it the same limit for SQL 2000 & 2005 ?
Also if I set /3GB in the boot.ini, can the memory be used up to 3Gb instead
of 2Gb ?Johnny wrote:
> I read somewhere that the SQL Standard edition can only use the
> memory up to 2Gb.
> Is it the same limit for SQL 2000 & 2005 ?
> Also if I set /3GB in the boot.ini, can the memory be used up to 3Gb
> instead of 2Gb ?
Indeed, SQL Server 2000 Standard Edition supports maximum 2GB of RAM.
However, SQL Server 2005 Standard Edition supports the maximum memory
supported by the Operating System.
On 32-bit systems, the user-mode virtual address space for each 32-bit
process is 2GB (or 3GB if you use the /3GB in boot.ini). However, most
32-bit OS-s support PAE and/or AWE. PAE allows the OS to access more
than 4GB of memory and AWE allows an application to allocate memory
beyond the 4GB limit.
For more information, see:
http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
http://msdn2.microsoft.com/en-US/library/ms143685.aspx
http://msdn2.microsoft.com/en-us/library/aa366778.aspx
http://msdn2.microsoft.com/en-us/library/aa366796.aspx
http://msdn2.microsoft.com/en-us/library/aa366527.aspx
Razvan Socol
SQL Server MVP|||Hi,
So the maximum memory limit for SQL2000 & SQL2005 is different.
In order to use more than 4Gb of memory in SQL2005, /PAE & AWE has to be
set. However, AWE is only available for SQL2005 Enterprise or Developer
edition. How Standard edition can use above 4Gb of memory.
From books online (dated April 2006).
"Support for AWE is available only in the Enterprise and Developer editions
and only applies to 32-bit operating systems. " (OR it is misleading ?)
Also from my experience, I did try to set AWE in SQL2005 standard edition
but it is not allowed. I cannot remember what the error message was. At the
end, I had to uninstall standard edition and reinstall enterprise edition.
Any ideas ? Thanks for your advices.
"Razvan Socol" wrote:
> Johnny wrote:
> > I read somewhere that the SQL Standard edition can only use the
> > memory up to 2Gb.
> > Is it the same limit for SQL 2000 & 2005 ?
> > Also if I set /3GB in the boot.ini, can the memory be used up to 3Gb
> > instead of 2Gb ?
> Indeed, SQL Server 2000 Standard Edition supports maximum 2GB of RAM.
> However, SQL Server 2005 Standard Edition supports the maximum memory
> supported by the Operating System.
> On 32-bit systems, the user-mode virtual address space for each 32-bit
> process is 2GB (or 3GB if you use the /3GB in boot.ini). However, most
> 32-bit OS-s support PAE and/or AWE. PAE allows the OS to access more
> than 4GB of memory and AWE allows an application to allocate memory
> beyond the 4GB limit.
> For more information, see:
> http://msdn2.microsoft.com/en-us/library/aa933149(SQL.80).aspx
> http://msdn2.microsoft.com/en-US/library/ms143685.aspx
> http://msdn2.microsoft.com/en-us/library/aa366778.aspx
> http://msdn2.microsoft.com/en-us/library/aa366796.aspx
> http://msdn2.microsoft.com/en-us/library/aa366527.aspx
>
> --
> Razvan Socol
> SQL Server MVP
>|||Johnny wrote:
> From books online (dated April 2006).
> "Support for AWE is available only in the Enterprise and Developer
> editions and only applies to 32-bit operating systems. " (OR it is
> misleading ?)
SQL Server 2005 Books Online (May 2007) says:
"Support for AWE is available only in the SQL Server 2005 Enterprise,
Standard, and Developer editions and only applies to 32-bit operating
systems."
See: http://msdn2.microsoft.com/en-us/library/ms187499.aspx
You can download SQL Server 2005 Books Online (May 2007) from:
http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4
220-b133-29c1e0b6585f
However, even if you are using AWE, you are still limited by the
maximum amount of RAM accessible by the Operating System. For example,
Windows Server 2003 Standard Edition (32-bit) can only use 4GB of RAM.
To access more than 4GB of RAM on a 32-bit Windows 2003 system, you
need Windows Server 2003 Enterprise Edition or Datacenter Edition.
See (again): http://msdn2.microsoft.com/en-us/library/aa366778.aspx
--
Razvan Socol
SQL Server MVP|||Thanks for your advices.
I know all these factors have to be considered (e.g windows Enterprise
edition).
What is the best way to find out how much memory the SQL Server is currently
using ? (from task manager to show memory usage or use performance monitor).
If using performance monitor, what are the counters needed to check ? (SQL
Server memory manager ?)
Regards,
Johnny
"Razvan Socol" wrote:
> Johnny wrote:
> > From books online (dated April 2006).
> > "Support for AWE is available only in the Enterprise and Developer
> > editions and only applies to 32-bit operating systems. " (OR it is
> > misleading ?)
> SQL Server 2005 Books Online (May 2007) says:
> "Support for AWE is available only in the SQL Server 2005 Enterprise,
> Standard, and Developer editions and only applies to 32-bit operating
> systems."
> See: http://msdn2.microsoft.com/en-us/library/ms187499.aspx
> You can download SQL Server 2005 Books Online (May 2007) from:
> http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4
> 220-b133-29c1e0b6585f
> However, even if you are using AWE, you are still limited by the
> maximum amount of RAM accessible by the Operating System. For example,
> Windows Server 2003 Standard Edition (32-bit) can only use 4GB of RAM.
> To access more than 4GB of RAM on a 32-bit Windows 2003 system, you
> need Windows Server 2003 Enterprise Edition or Datacenter Edition.
> See (again): http://msdn2.microsoft.com/en-us/library/aa366778.aspx
> --
> Razvan Socol
> SQL Server MVP
>|||Johnny wrote:
> What is the best way to find out how much memory the SQL Server is
> currently using ? (from task manager to show memory usage or use
> performance monitor). If using performance monitor, what are the
> counters needed to check ? (SQL Server memory manager ?)
I'm not sure about the best way, but one way would be DBCC MEMORYSTATUS.
--
Razvan Socol
SQL Server MVP|||You can also take a look at the following page:
SQL Server 2005 - Monitoring Memory Usage
http://msdn2.microsoft.com/en-us/library/ms176018.aspx
Ekrem Ã?nsoy
http://www.ekremonsoy.net , http://ekremonsoy.blogspot.com
MCBDA, MCTS: SQL Server 2005, MCITP:DBA, MCSD.Net, MCSE, MCBMSP, MCT
"Johnny" <Johnny@.discussions.microsoft.com> wrote in message
news:D86727A8-C8DB-4713-BB0A-A146991F5662@.microsoft.com...
> Thanks for your advices.
> I know all these factors have to be considered (e.g windows Enterprise
> edition).
> What is the best way to find out how much memory the SQL Server is
> currently
> using ? (from task manager to show memory usage or use performance
> monitor).
> If using performance monitor, what are the counters needed to check ? (SQL
> Server memory manager ?)
> Regards,
> Johnny
>
> "Razvan Socol" wrote:
>> Johnny wrote:
>> > From books online (dated April 2006).
>> > "Support for AWE is available only in the Enterprise and Developer
>> > editions and only applies to 32-bit operating systems. " (OR it is
>> > misleading ?)
>> SQL Server 2005 Books Online (May 2007) says:
>> "Support for AWE is available only in the SQL Server 2005 Enterprise,
>> Standard, and Developer editions and only applies to 32-bit operating
>> systems."
>> See: http://msdn2.microsoft.com/en-us/library/ms187499.aspx
>> You can download SQL Server 2005 Books Online (May 2007) from:
>> http://www.microsoft.com/downloads/details.aspx?FamilyID=be6a2c5d-00df-4
>> 220-b133-29c1e0b6585f
>> However, even if you are using AWE, you are still limited by the
>> maximum amount of RAM accessible by the Operating System. For example,
>> Windows Server 2003 Standard Edition (32-bit) can only use 4GB of RAM.
>> To access more than 4GB of RAM on a 32-bit Windows 2003 system, you
>> need Windows Server 2003 Enterprise Edition or Datacenter Edition.
>> See (again): http://msdn2.microsoft.com/en-us/library/aa366778.aspx
>> --
>> Razvan Socol
>> SQL Server MVP