MDAC version error

Hi,
I have a problem to install SQL Server 2000 Development Edition onto my
Windows 2000 professional P.,I have a check of my MDAC version using the
Component Checker, it tells that the version of my MDAC is 2.53.6202.0 which
should be 2.53.6200.0.
Does anybody know why this happened and how to solve it?
Thanks in advance
FrankThe Component Checker you are using likely had not been updated for the
security patch you have installed. If you get a newer version of the
Component Checker
(http://msdn.microsoft.com/library/default.asp?url=/downloads/list/dataacces
s.asp) it should report 2.53.6202.
Shawn Aebi
Microsoft
This posting is provided "AS IS" with no warranties, and confers no rights.

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'
> >

MDAC 2.1 / MDAC 2.53

HI,
SQL Server 7.0 (sp4)
Production machine : SQL Server 7.0 (sp4) Entreprise Edition on NT
--> MDAC 2.1,2 sp2
Test machine : SQL Server 7.0 (sp4) Standard Edition on Windows
2000 --> MDAC 2.53
I would like my Test machine be like my Production Machine.
In others words, I would like to change from MDAC 2.53 to MDAC 2.1.2 sp2 on
my Test machine.
Is it possible ? If yes, how can I do that ? (with Mdac_typ.exe ?)
Thank you
DannyDanny,
MDAC is a system component on Windows 2000 and XP and 2003. You cannot
removed it and I am sure that you cannot downgrade it from 2.5. MDAC 2.5 has
problems with DTS when connecting to MDAC 2.1. So you are better off
upgrading your server level to be the same as the workstation.
Chris Wood
Alberta Department of Energy
CANADA
"Danny Presse" <dpresse@.congresmtl.com> wrote in message
news:uwczaaWTDHA.2280@.TK2MSFTNGP12.phx.gbl...
> HI,
> SQL Server 7.0 (sp4)
> Production machine : SQL Server 7.0 (sp4) Entreprise Edition on NT
> --> MDAC 2.1,2 sp2
> Test machine : SQL Server 7.0 (sp4) Standard Edition on Windows
> 2000 --> MDAC 2.53
> I would like my Test machine be like my Production Machine.
> In others words, I would like to change from MDAC 2.53 to MDAC 2.1.2 sp2
on
> my Test machine.
> Is it possible ? If yes, how can I do that ? (with Mdac_typ.exe ?)
> Thank you
> Danny
>

Maximum number of connections

Hi,

Could somebody tell what is the maximum number of concurrent connections that are supported in sql server 2005 developer edition?

thanks

SQL Server allowed 32767 connections per instance in SQL 2000. I don′t think they lowered it down. With 16 instances you could theoretically come up to 524272 connections (which is sort of unbelievable). I don′t know if your question has only an academic flavour or how many can be instantiated in the real world.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

Thanks jens but i'm talking with reference to the information posted here : http://channel9.msdn.com/ShowPost.aspx?PostID=173513

i'm pasting the relevant excerpts below.i'm only concerned with the information in red.

============================================================

Tyler Brown
Bullets change governments far surer than votes.

Mon, Mar 20 2006 4:55 PM

I'm not sure about the Express edition, but from what I understand, the Developer Edition is a full featured edition with minimal CAL's. It's meant for use in a development environment, and not a production environment, so it restricts the number of connections.

ben2004uk

Mon, Mar 20 2006 5:05 PM

AFAIK (Don't quote me) the Express has a connection limit of 25 and is designed for low-end apps / websites.

irascian
Irascible Ian

Mon, Mar 20 2006 5:42 PM

The others have answered it really. "Express" is the free lightweight version. "Developer" is the full Enterprise version with all the bells and whistles for developers to work against but limited in terms of CALs.

Ordinarily if you can get hold of it Developer Edition is the version to install, with one exception: Team Foundation Server doesn't support it and you need the Standard, Professional or Enterprise edition for that.
========================================================

Now my problem :

1) "Developer Edition is a full featured edition with minimal CAL's."

what is this minimal CAL?

2) "Express has a connection limit of 25 "

what is the connection limit for the developer edition?

Looking forward to ur reply

thanks

|||

Hi,

I don′t know about any limitation in Developer Edition, though its full featured. SQL Expresses only limitation are written in here:

http://msdn2.microsoft.com/en-us/library/ms165672.aspx

Keep in mind that the query governour has been removed, so the limitation of the MSDE is no longer valid.

HTH, Jens Suessmeyer.

http://msdn2.microsoft.com/en-us/library/ms165672.aspx

Keep in mind that the query governour has been removed, so the limitation of the MSDE is no longer valid.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

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 for standart edition / enterprise

Hello there
I am runing on sql 7 environment and planing to move to 2k environment
(quite late but.....).
for one of the databases, I have a server with 4G of ram but I have only sql
server standart, I am wondering if it will still take 4 G of ram since MS
claims it will take only 2 G?
for some reason I heard that it can utilize the full 4G ?
another thing is: I have licenses for 1 processor, do you guys know if I can
upgrade that to 2?
thanks !
Hi,
SQL Standard edition can only use 2 GB RAM at the max. To utilize more you
have to use SQL Server Enterprise edition.
I have licenses for 1 processor, do you guys know if I can upgrade that to
2?
http://www.microsoft.com/sql/howtobuy/default.asp
Thanks
Hari
MCDBA
"simo sentissi" <simo_sentissi@.skc.edu> wrote in message
news:OVG$ndQZEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello there
> I am runing on sql 7 environment and planing to move to 2k environment
> (quite late but.....).
> for one of the databases, I have a server with 4G of ram but I have only
sql
> server standart, I am wondering if it will still take 4 G of ram since MS
> claims it will take only 2 G?
> for some reason I heard that it can utilize the full 4G ?
> another thing is: I have licenses for 1 processor, do you guys know if I
can
> upgrade that to 2?
>
> thanks !
>

Maximum Memory for standart edition / enterprise

Hello there
I am runing on sql 7 environment and planing to move to 2k environment
(quite late but.....).
for one of the databases, I have a server with 4G of ram but I have only sql
server standart, I am wondering if it will still take 4 G of ram since MS
claims it will take only 2 G'
for some reason I heard that it can utilize the full 4G ?
another thing is: I have licenses for 1 processor, do you guys know if I can
upgrade that to 2?
thanks !Hi,
SQL Standard edition can only use 2 GB RAM at the max. To utilize more you
have to use SQL Server Enterprise edition.
I have licenses for 1 processor, do you guys know if I can upgrade that to
2?
http://www.microsoft.com/sql/howtobuy/default.asp
Thanks
Hari
MCDBA
"simo sentissi" <simo_sentissi@.skc.edu> wrote in message
news:OVG$ndQZEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello there
> I am runing on sql 7 environment and planing to move to 2k environment
> (quite late but.....).
> for one of the databases, I have a server with 4G of ram but I have only
sql
> server standart, I am wondering if it will still take 4 G of ram since MS
> claims it will take only 2 G'
> for some reason I heard that it can utilize the full 4G ?
> another thing is: I have licenses for 1 processor, do you guys know if I
can
> upgrade that to 2?
>
> thanks !
>

Maximum Memory for standart edition / enterprise

Hello there
I am runing on sql 7 environment and planing to move to 2k environment
(quite late but.....).
for one of the databases, I have a server with 4G of ram but I have only sql
server standart, I am wondering if it will still take 4 G of ram since MS
claims it will take only 2 G'
for some reason I heard that it can utilize the full 4G ?
another thing is: I have licenses for 1 processor, do you guys know if I can
upgrade that to 2?
thanks !Hi,
SQL Standard edition can only use 2 GB RAM at the max. To utilize more you
have to use SQL Server Enterprise edition.
I have licenses for 1 processor, do you guys know if I can upgrade that to
2?
http://www.microsoft.com/sql/howtobuy/default.asp
Thanks
Hari
MCDBA
"simo sentissi" <simo_sentissi@.skc.edu> wrote in message
news:OVG$ndQZEHA.1652@.TK2MSFTNGP09.phx.gbl...
> Hello there
> I am runing on sql 7 environment and planing to move to 2k environment
> (quite late but.....).
> for one of the databases, I have a server with 4G of ram but I have only
sql
> server standart, I am wondering if it will still take 4 G of ram since MS
> claims it will take only 2 G'
> for some reason I heard that it can utilize the full 4G ?
> another thing is: I have licenses for 1 processor, do you guys know if I
can
> upgrade that to 2?
>
> thanks !
>

Maximum Memory Configurations

What is the maximum amount of memory SQL2K can address per instance using the following configuration
WIN 2003 32 bit Enterprise Edition OS with 32 GB RAM
SQL2K SP3 32 bit Enterprise Edition w/ hot fixes
AWE Enabled
/PAE switch in boot.ini
Lock pages in memory enabled for MSSQL Service Account.
The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K Advanced Server but has no mention of max memory allowed.
It is my understanding that each instance will be able to use all of its =
addressable RAM. In your scenario you could configure three instances =
to use 8GB of RAM and you could have a fourth using 4GB of RAM. That =
would allow 4GB of free memory for the OS to work with. Of course you =
could install more instances, but you would want to limit the amount of =
RAM each uses so that you do not run into problems by trying to allocate =
more memory than you have in the server.=20
--=20
Keith
"Douglas Luke" <anonymous@.discussions.microsoft.com> wrote in message =
news:D6F9605B-497D-49C6-9BED-FF0B19B83BC9@.microsoft.com...
> What is the maximum amount of memory SQL2K can address per instance =
using the following configuration
>=20
> WIN 2003 32 bit Enterprise Edition OS with 32 GB RAM
> SQL2K SP3 32 bit Enterprise Edition w/ hot fixes
> AWE Enabled
> /PAE switch in boot.ini
> Lock pages in memory enabled for MSSQL Service Account.
>=20
> The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K =
Advanced Server but has no mention of max memory allowed.

Maximum Memory Configurations

What is the maximum amount of memory SQL2K can address per instance using the following configuratio
WIN 2003 32 bit Enterprise Edition OS with 32 GB RA
SQL2K SP3 32 bit Enterprise Edition w/ hot fixe
AWE Enable
/PAE switch in boot.in
Lock pages in memory enabled for MSSQL Service Account
The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K Advanced Server but has no mention of max memory allowed.It is my understanding that each instance will be able to use all of its =addressable RAM. In your scenario you could configure three instances =to use 8GB of RAM and you could have a fourth using 4GB of RAM. That =would allow 4GB of free memory for the OS to work with. Of course you =could install more instances, but you would want to limit the amount of =RAM each uses so that you do not run into problems by trying to allocate =more memory than you have in the server.
-- Keith
"Douglas Luke" <anonymous@.discussions.microsoft.com> wrote in message =news:D6F9605B-497D-49C6-9BED-FF0B19B83BC9@.microsoft.com...
> What is the maximum amount of memory SQL2K can address per instance =using the following configuration
> > WIN 2003 32 bit Enterprise Edition OS with 32 GB RAM
> SQL2K SP3 32 bit Enterprise Edition w/ hot fixes
> AWE Enabled
> /PAE switch in boot.ini
> Lock pages in memory enabled for MSSQL Service Account.
> > The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K =Advanced Server but has no mention of max memory allowed.

Maximum Memory Configurations

What is the maximum amount of memory SQL2K can address per instance using th
e following configuration
WIN 2003 32 bit Enterprise Edition OS with 32 GB RAM
SQL2K SP3 32 bit Enterprise Edition w/ hot fixes
AWE Enabled
/PAE switch in boot.ini
Lock pages in memory enabled for MSSQL Service Account.
The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K Advanced Se
rver but has no mention of max memory allowed.It is my understanding that each instance will be able to use all of its =
addressable RAM. In your scenario you could configure three instances =
to use 8GB of RAM and you could have a fourth using 4GB of RAM. That =
would allow 4GB of free memory for the OS to work with. Of course you =
could install more instances, but you would want to limit the amount of =
RAM each uses so that you do not run into problems by trying to allocate =
more memory than you have in the server.=20
--=20
Keith
"Douglas Luke" <anonymous@.discussions.microsoft.com> wrote in message =
news:D6F9605B-497D-49C6-9BED-FF0B19B83BC9@.microsoft.com...
> What is the maximum amount of memory SQL2K can address per instance =
using the following configuration
>=20
> WIN 2003 32 bit Enterprise Edition OS with 32 GB RAM
> SQL2K SP3 32 bit Enterprise Edition w/ hot fixes
> AWE Enabled
> /PAE switch in boot.ini
> Lock pages in memory enabled for MSSQL Service Account.
>=20
> The BOL says SQL2K 32 bit can address up to 8 GB of RAM on Win2K =
Advanced Server but has no mention of max memory allowed.

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

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

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

Maximum databases on SQL Server 2000

We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
This server is being used for heavy analysis by 10 heveyduty workstations.
We have more then 1000 databases on this server.
Should we limit the databases on this server ? we are having issues with
performance and SQL service stopping frequently..
Please advise
Probably. I'd be surprised you can keep all 1000 open and working at the
same time. Memory, disks, bus, etc... are all probably pretty upset with
their deplorable work conditions. :-)
Figure out which of your 1000 databases are most heavily used and move them
out first. Perfmon and Profiler are probably gonna be your new buddies if
they aren't already.
Btw, perf issues aside, 1000 databases in one instance is probably not much
fun to manage. Just expanding the object browser takes a while. What about
maintenance operations? Look up multi instance in BOL and give it some
serious thought. Life will probably be at least a little better that way.
joe.
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:37CBC0C7-C1FA-4FE5-9851-B101A5E8E88D@.microsoft.com...
> We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
> This server is being used for heavy analysis by 10 heveyduty
> workstations.
> We have more then 1000 databases on this server.
> Should we limit the databases on this server ? we are having issues with
> performance and SQL service stopping frequently..
> Please advise

Maximum databases on SQL Server 2000

We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
This server is being used for heavy analysis by 10 heveyduty workstations.
We have more then 1000 databases on this server.
Should we limit the databases on this server ? we are having issues with
performance and SQL service stopping frequently..
Please adviseProbably. I'd be surprised you can keep all 1000 open and working at the
same time. Memory, disks, bus, etc... are all probably pretty upset with
their deplorable work conditions. :-)
Figure out which of your 1000 databases are most heavily used and move them
out first. Perfmon and Profiler are probably gonna be your new buddies if
they aren't already.
Btw, perf issues aside, 1000 databases in one instance is probably not much
fun to manage. Just expanding the object browser takes a while. What about
maintenance operations? Look up multi instance in BOL and give it some
serious thought. Life will probably be at least a little better that way.
joe.
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:37CBC0C7-C1FA-4FE5-9851-B101A5E8E88D@.microsoft.com...
> We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
> This server is being used for heavy analysis by 10 heveyduty
> workstations.
> We have more then 1000 databases on this server.
> Should we limit the databases on this server ? we are having issues with
> performance and SQL service stopping frequently..
> Please advise

Maximum databases on SQL Server 2000

We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
This server is being used for heavy analysis by 10 heveyduty workstations.
We have more then 1000 databases on this server.
Should we limit the databases on this server ? we are having issues with
performance and SQL service stopping frequently..
Please adviseProbably. I'd be surprised you can keep all 1000 open and working at the
same time. Memory, disks, bus, etc... are all probably pretty upset with
their deplorable work conditions. :-)
Figure out which of your 1000 databases are most heavily used and move them
out first. Perfmon and Profiler are probably gonna be your new buddies if
they aren't already.
Btw, perf issues aside, 1000 databases in one instance is probably not much
fun to manage. Just expanding the object browser takes a while. What about
maintenance operations? Look up multi instance in BOL and give it some
serious thought. Life will probably be at least a little better that way.
joe.
"Dave" <Dave@.discussions.microsoft.com> wrote in message
news:37CBC0C7-C1FA-4FE5-9851-B101A5E8E88D@.microsoft.com...
> We have a Dell 2650 server with 3 GB of ram ( SQL Staandard edition )
> This server is being used for heavy analysis by 10 heveyduty
> workstations.
> We have more then 1000 databases on this server.
> Should we limit the databases on this server ? we are having issues with
> performance and SQL service stopping frequently..
> Please advise

Maximum connections for SQL 2000 Developer Edition

I can't seem to find this info online anywhere. What's
the maximum connections for SQL 2000 Developer Edition?
We have a server running several instances of Developer
edition so does they have the share these connections or
is it a max connections per instance?
Thanks,
Van
Hi
Technically 32 737 per instance, but you will run out of TCP ports long
before a multi-instance installation can max out.
Developer Edition is Enterprise Edition with licensing limitations.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Van Jones" <anonymous@.discussions.microsoft.com> wrote in message
news:129201c55266$1fbd2b00$a601280a@.phx.gbl...
>I can't seem to find this info online anywhere. What's
> the maximum connections for SQL 2000 Developer Edition?
> We have a server running several instances of Developer
> edition so does they have the share these connections or
> is it a max connections per instance?
> Thanks,
> Van

Maximum Capacity supported by SQL Server 2000 Enterprise under Windows Server 2003 Enterprise

Hello

Does anyone know what is the maximum capacity supported by SQL Server 2000 Enterprise Edition running under Windows Server 2003 Enterprise Edition in terms of number of CPU and amount of RAM.?

For CPU : Windows Server 2003 EE supported up to 8 CPU so I assume SQL 2000 Enterprise can also support up to 8 CPU

For memory: Windows Server 2003 EE (32 bits) can support up to 32 GB of RAM so I am wondering whether SQL 2000 EE can also support up to 32 GB ? Under BOL it said it could support up to 8 GB of RAM under Windows 2000 Advance server but it does not mention Windows Server 2003 EE?

Hi Kay. SQL Server support for memory and CPU generally follows the same supported limits for the OS it is running on. Which means for memory, SQL Server supports the use of up to 32gb of RAM on Windows 2003 Enterprise, and up to 64gb of RAM with Windows 2003 Datacenter. For CPU, Windows Server 2003 Enterprise pushes up to at least 16 CPUs I believe, possibly 32 now...perhaps someone else can verify this for sure, but I believe those are the correct numbers.

HTH

|||

Hi Chad.

I found a reference at the Microsoft Web site on Windows Server 2003 comparions. It seems to indicate that Enterprise Edition only supports up to 8-way (for both SP1 and R2) for processor. For memory it can support up to 64 GB in RAM and 1 TB for x64 and Itanium versions.

http://www.microsoft.com/windowsserver2003/evaluation/features/comparefeatures.mspx#Hardware%20Specifications

Thanks for your answer on the questions regarding the memory supported by SQL. I am planning to upgrade our server to max CPU & RAM and I want to make sure that SQL can take the advantage of the additional hardware.

MAXFILE Size won't Change

SQL Server 2005 64 Bit Enterprise Edition.

When I run the the following command I get command completed successfully.

ALTER DATABASE Apollo_Replication
MODIFY FILE (NAME = Apollo_Replication_log,
MAXSIZE = 'UNLIMITED')

However

when I look at the database properties the file growth is still

restricted to 2 GB. I even tried to edit the property through

SSMS. Same results...It looks like it saves ok but when I go back

in... no change.
The only thing unique about the db is it is the subscriber from an Oracle publisher.
Has anyone seen this little feature before?Are you sure it is 2GB and not 2TB? The architectural limit for each log file is 2TB.|||oops it is 2 TB. But why can't I change the properties to unlimited file growth? My current size is 31 GB. I am trying to shrink the file back down to a reasonable size and change the properties.|||

UNLIMITED is never really unlimited. For log files it is 2TB. For data files it is actually 16TB. Its just a reporting issue on what the UI or report considers to be "unlimited."