MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian
> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057

> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> http://www.aspfaq.com/2057
on
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
|||Ian wrote:

> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function
|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
2.8
> on
>
|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>
|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> 2.8
>

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057

> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
http://www.aspfaq.com/
(Reverse address to reply.)|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> http://www.aspfaq.com/2057
>
on[vbcol=seagreen]
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?|||Ian wrote:

> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
2.8[vbcol=seagreen]
> on
>|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> 2.8
>

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian
> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057

> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
http://www.aspfaq.com/
(Reverse address to reply.)
|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> http://www.aspfaq.com/2057
on
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>
|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
|||Ian wrote:

> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function
|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...[vbcol=seagreen]
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
2.8
> on
>
|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>
|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> 2.8
>

MDAC version

Hi
How can I find out what version of MDAC is installed on a Machine.
And would there be any problem with me installing both MDAC 2.7 and 2.8 on
the same machine
Ian> How can I find out what version of MDAC is installed on a Machine.
http://www.aspfaq.com/2057
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
Installing 2.8 should upgrade 2.7 to 2.8.
--
http://www.aspfaq.com/
(Reverse address to reply.)|||Thanks Aaron
But i was reading that MDAC 2.8 does not have the JET drivers and my
application needs them as well as the MS SQL drivers.
So do i install both?
Ian
"Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > How can I find out what version of MDAC is installed on a Machine.
> http://www.aspfaq.com/2057
> > And would there be any problem with me installing both MDAC 2.7 and 2.8
on
> > the same machine
> Installing 2.8 should upgrade 2.7 to 2.8.
> --
> http://www.aspfaq.com/
> (Reverse address to reply.)
>|||No, you don't need to install 2.7 and 2.8. You need to install MDAC 2.8 and
then install newer jet drivers separately.
http://www.aspfaq.com/2342
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?|||Ian wrote:
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
I use this approach:
Private Sub mnuHelpMDAC_Click()
Dim ans As String
ans = GetAdoVersion
If ans = "0" Then
MsgBox "MDAC is not Installed" & _
"Please Install MDAC from the DBAdmin CD", _
vbCritical, "Missing Important Component"
Else
MsgBox "MDAC version " & ans & " Is Installed on this System"
End If
End Sub
Function GetAdoVersion() As String
'Retrieve ADO (MDAC) version - see if it installed
'Returns an empty string is ADO is not installed
Dim o As Object
On Error Resume Next
GetAdoVersion = "0"
Set o = CreateObject("ADODB.Connection")
If Err.Number = 0 Then GetAdoVersion = o.Version
Set o = Nothing
End Function|||MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last version
that did.
In any case, Aaron gave you the correct answer
--
Doug Steele, Microsoft Access MVP
http://I.Am/DougSteele
(no e-mails, please!)
"Ian" <ian@.NoWhere.com> wrote in message
news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> Thanks Aaron
> But i was reading that MDAC 2.8 does not have the JET drivers and my
> application needs them as well as the MS SQL drivers.
>
> So do i install both?
> Ian
>
>
> "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > > How can I find out what version of MDAC is installed on a Machine.
> >
> > http://www.aspfaq.com/2057
> >
> > > And would there be any problem with me installing both MDAC 2.7 and
2.8
> on
> > > the same machine
> >
> > Installing 2.8 should upgrade 2.7 to 2.8.
> >
> > --
> > http://www.aspfaq.com/
> > (Reverse address to reply.)
> >
> >
>|||Thank you all
For the advice.
"Ian" <ian@.NoWhere.com> wrote in message
news:u4iDeidiEHA.3016@.tk2msftngp13.phx.gbl...
> Hi
> How can I find out what version of MDAC is installed on a Machine.
> And would there be any problem with me installing both MDAC 2.7 and 2.8 on
> the same machine
> Ian
>|||And to offer some more advice, unless there is a compelling reason to use
ADO 2.6 or greater, just reference ADO 2.5 and redistribute MDAC 2.5. That
way, the Jet components are included and, if not present, should get
installed even if MDAC 2.6 or greater is already installed. At least, I'm
pretty sure about that. I'm sure someone will correct me if I'm wrong.
Mike
"Douglas J. Steele" <NOSPAM_djsteele@.NOSPAM_canada.com> wrote in message
news:untEKfiiEHA.1104@.TK2MSFTNGP10.phx.gbl...
> MDAC 2.7 doesn't have the Jet drivers either: MDAC 2.5 was the last
version
> that did.
> In any case, Aaron gave you the correct answer
> --
> Doug Steele, Microsoft Access MVP
> http://I.Am/DougSteele
> (no e-mails, please!)
>
> "Ian" <ian@.NoWhere.com> wrote in message
> news:uotFj7diEHA.384@.TK2MSFTNGP10.phx.gbl...
> > Thanks Aaron
> >
> > But i was reading that MDAC 2.8 does not have the JET drivers and my
> > application needs them as well as the MS SQL drivers.
> >
> >
> > So do i install both?
> >
> > Ian
> >
> >
> >
> >
> > "Aaron [SQL Server MVP]" <ten.xoc@.dnartreb.noraa> wrote in message
> > news:ub99mydiEHA.1344@.TK2MSFTNGP11.phx.gbl...
> > > > How can I find out what version of MDAC is installed on a Machine.
> > >
> > > http://www.aspfaq.com/2057
> > >
> > > > And would there be any problem with me installing both MDAC 2.7 and
> 2.8
> > on
> > > > the same machine
> > >
> > > Installing 2.8 should upgrade 2.7 to 2.8.
> > >
> > > --
> > > http://www.aspfaq.com/
> > > (Reverse address to reply.)
> > >
> > >
> >
> >
>

MDAC upgrade problem CompCheck reports 2.5 instead of 2.8

I am running SQL server on a Windows 2000 server with sp4 installed. After installing SQL service pack 4 on the machine my applications began complaining that MDAC was version 2.5 sure enough CompChecker reports version 2.5. I have tried to install the latest version of MDAC (2.8) on the machine but no matter what I do CompChecker reports 2.5.

I've tried reinstalling the SQL service pack I had no luck with that. Any help with this issue would be greatly appreciated.

WHen was the Windows service pack4 was applied, is it after SQL SP4 or before?

Check this KBA http://support.microsoft.com/kb/823939 for informaiton, ifyou need then you have to install MDAC 2.8 seperately.

|||The service pack was applied before the upgrade.|||I don't know if this helps but I think the issue is with the Windows File Protection. If I attempt to rename one of the dlls the server will automatically replace the file on the server with the 2.5 version. Is there some way to overcome this?|||Did you try to install the MDAC 2.8 separately like Satya proposed ? The file cannot be changed as the Windows FileProtextion is enabled for them (as you already noticed). if you already tried to install the MDAC 2.8, did you get an error or did the install run through ? Did you restart the system afterwards ?

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||

I finally figured this out. It turns out that there were certain registry settings that were incorrectly set when SP4 was applied to SQL Server 2000. I don't want to get into the exact registry settings that need to be changed but that is where the answer lies.

Thanks to all for your assistance.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

sql

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

MDAC 2.8 Fatal Setup Error. This setup does not support installing on this operating system

I have XP Pro SP2 with MDAC 2.8.1022. It had a problem so I tried to reinstall MDAC and got a Fatal Setup Error. This setup does not support installing on this operating system. I downloaded MDAC 2.8 1177 and get the same error.

I thought of uninstalling/reinstalling SP2, but this is a 2 month old Dell Latitude 610 with factory installed XP. There is no Windows Service Pack 2 option listed in the Control Panel > Add/Remove Programs.

There's some other strange things, so I wonder if they are related.

1) I have Paul set up as an administrator account. Some folders like MSSQL show that account with no permissions. I grant all the permissions to Paul for that folder. I come back later and the permissions are gone.

2) I deleted 20 files in Explorer, but 7 of them did not go away. I deleted those 7 again and they instatnly reappeared. I deleted those 7 again and then they finally went away.

3) I get a slow reaction time for things like Windows Explorer and opening and closing programs. This is suprising since it has 2 gig of RAM and 2.3 Gig processor. Could it be a memory handling problem that's causing OS problems. Probably, the memory didn't handle the OS installation well and the whole system is compromised now.

I'm having the same problem on XP Sp2 trying to re-install MDAC.

Thought I'd try re-installing MDAC since my system errors out when I try to register DLL files.

|||

I've seen this error during MDAC installation on XP SP2 as well. I was able to get around it by changing the Compatibility Properties of the mdac installation file to Win NT. It then installs OK.

|||

Chnaces are the files did go away for an instant but they are on the system recovery list and XP replaced them.

|||

I have XP Pro SP2 . It had a problem so I tried to install ADO.Net (MDAC Version 2.8 SP1 ) many times and reload it from download.microsoft.com. I couldn't install on my computer. I get the Fatal Setup Error "This setup does not support installing on this operating system". How can I solve this problem ?

|||

I could not overcome the problem.. I finally did erased the drive and reinstalled windows.

Paul

|||Windows XP comes pre-installed with MDAC you should not install the standalone MDAC installer on Windows XP. If you have a problem with the MDAC install on XP then just run a repair install of XP this will reinstall the MDAC that XP ships with.|||

I had a similar experience. Two possible options can be used to allow XP to repair the entries or force the install without having to repair the XP installation.

1. To repair your MDAC installation. Found this solution on the web that works. Have your XP SP2 install disk handy. Go to and find c:\windows\inf\mdac.inf. Right click on the .inf file and pick Install. It will attempt to reinstall the files. Browse to source files on the XP CD. It should install smoothly. It may ask for the handler.reg (in c:\program files\common files\system\msadc\). Restart. Sign in (admin) and then after a few minutes windows update will want to apply the security patch again. You may want to follow up with the SJet update also.

2. To force the installation. Found this one also. XP SP2 will already have the SP1 update applied but has registry corruption (virus after affects). Right click on the MDAC 2.8 SP1 install exe file and select properties. Select the Compatability tab, check the compatability mode box and pick "windows NT" or possibly "Windows 2000". Click apply and run the file again. It should install all the proper files again.

This restored the complete connectivity to databases. In visual studio the data tables did not display properly with a flawed connection. If the access (mdb) tables display properly, then a connection to the SQL database (mdf) - missing tables -is a access/login rights problem. Grant login rights to the user for the database.

|||

John,

#2 works like a charms. Thanks a million.

MDAC

Hi,
I have a problem installing MDAC 2.8 on a client computer. When I perform
the install here is what happens:
Scanning for programs using MDAC. It just hangs here and never finishes the
install.
Any ideas on how to install it?
K.J.B.
Kelly,
'HOWTO: MDAC Setup Troubleshooting Guide'
http://support.microsoft.com/?id=232060
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"K.J.B." <kelly.burch@.khgcga.com> wrote in message
news:#2v2zcPREHA.3672@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a problem installing MDAC 2.8 on a client computer. When I perform
> the install here is what happens:
> Scanning for programs using MDAC. It just hangs here and never finishes
the
> install.
> Any ideas on how to install it?
> K.J.B.
>
>
>
|||The service "WinLogon.Exe" is using MDAC but I cannot stop this service...
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:%23W%23UsUrREHA.1396@.TK2MSFTNGP12.phx.gbl...[vbcol=seagreen]
> Kelly,
> 'HOWTO: MDAC Setup Troubleshooting Guide'
> http://support.microsoft.com/?id=232060
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "K.J.B." <kelly.burch@.khgcga.com> wrote in message
> news:#2v2zcPREHA.3672@.TK2MSFTNGP10.phx.gbl...
perform
> the
>

MDAC

Hi,
I have a problem installing MDAC 2.8 on a client computer. When I perform
the install here is what happens:
Scanning for programs using MDAC. It just hangs here and never finishes the
install.
Any ideas on how to install it?
K.J.B.Kelly,
'HOWTO: MDAC Setup Troubleshooting Guide'
http://support.microsoft.com/?id=232060
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"K.J.B." <kelly.burch@.khgcga.com> wrote in message
news:#2v2zcPREHA.3672@.TK2MSFTNGP10.phx.gbl...
> Hi,
> I have a problem installing MDAC 2.8 on a client computer. When I perform
> the install here is what happens:
> Scanning for programs using MDAC. It just hangs here and never finishes
the
> install.
> Any ideas on how to install it?
> K.J.B.
>
>
>|||The service "WinLogon.Exe" is using MDAC but I cannot stop this service...
"Dinesh T.K" <tkdinesh@.nospam.mail.tkdinesh.com> wrote in message
news:%23W%23UsUrREHA.1396@.TK2MSFTNGP12.phx.gbl...
> Kelly,
> 'HOWTO: MDAC Setup Troubleshooting Guide'
> http://support.microsoft.com/?id=232060
> --
> Dinesh
> SQL Server MVP
> --
> --
> SQL Server FAQ at
> http://www.tkdinesh.com
> "K.J.B." <kelly.burch@.khgcga.com> wrote in message
> news:#2v2zcPREHA.3672@.TK2MSFTNGP10.phx.gbl...
perform[vbcol=seagreen]
> the
>sql

McAfee AV Install

We will be installing McAfee AV onto our Active/Passive cluster environment
and I would like to know if we need to make any exclusions to specific files
or folders or if there is a particular way the product needs installed so
operations are not disrupted?
Lee K Harlee.harris@.berbee.com
Check out:
http://msdn2.microsoft.com/en-us/library/ms189910.aspx
http://support.microsoft.com/kb/250355
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA, MCITP, MCTS
SQL Server MVP
Toronto, ON Canada
..
"Lee K Harris" <lee.harris@.berbee.com> wrote in message
news:0ABA9FD1-D975-49B0-9F28-A3CD08F6761E@.microsoft.com...
We will be installing McAfee AV onto our Active/Passive cluster environment
and I would like to know if we need to make any exclusions to specific files
or folders or if there is a particular way the product needs installed so
operations are not disrupted?
Lee K Harlee.harris@.berbee.com

MaxLocksPerFile

Hi

I wrote a script in Installshield that changes the MaxLocksPerFile value in
Registry for Jet 3.x and Jet 4.0
While installing the application through Installshield, the custom value for
MaxLocksPerFile is being overwritten to 9500 in Registry for Jet
4.0(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0) but not
for Jet 3.x(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x).
The value is being overwritten to 9500 before the control reaches at the
script code.

I am wondering from where this 9500 value is being retrieved and set in
Registry.
Is there some file where these default values are mentioned.
If so then why 9500 value is not being set for Jet 3.x and is being set only
for Jet 4.0.

i am using MS Office 2002. Drivers for ODBC MS Access is above 4.0
and Installshield Version is 5.5.

Please help me to resolve this Issue.

-Regards
Harpreet

The default value for both Jet 3.5 and 4.0 is 9500.

If your installation script is causing Jet to be re-registered it will reset the values in the registry back to their defaults and over write yours.

The 9500 value was originally put in for Netware servers and typically you do not need to change it from its default pf 9500.

See page 611 of "The Jet Database Engine Programmers Guide" or futher searching of MSDN.

|||

Hi Joel,

Thanx for your reply.

Could you please let me know from where this default value of 9500 is retrieved and set the registry variable.

Could you please get me access to "The Jet Database Engine Programmers Guide" . I currently do not have this guide.

-Regards

Harpreet

|||

Here is a link to the book on Amazon:

http://www.amazon.com/Microsoft-Database-Programmers-Professional-Editions/dp/B00005TNX9

The registry is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Jet 4.0\MaxLocksPerFile

default is 9500

|||

Hi Joel

Thanks for the information.

Still I have one question: Is there some file (configuration file or so) from where this default value of 9500 is taken and set in to the registry.

-Regards

Harpreet

|||The registry value is created in setup or when registering msjet40.dll.|||

HI Joel,

Can we change this registry value during registering.We have _drivers.ini file which contains default values for arguments.I tried to set the custom value in that ini file, but during installation, registry value is again set to default value of 9500.

sql

MaxLocksPerFile

Hi

I wrote a script in Installshield that changes the MaxLocksPerFile value in
Registry for Jet 3.x and Jet 4.0
While installing the application through Installshield, the custom value for
MaxLocksPerFile is being overwritten to 9500 in Registry for Jet
4.0(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0) but not
for Jet 3.x(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x).
The value is being overwritten to 9500 before the control reaches at the
script code.

I am wondering from where this 9500 value is being retrieved and set in
Registry.
Is there some file where these default values are mentioned.
If so then why 9500 value is not being set for Jet 3.x and is being set only
for Jet 4.0.

i am using MS Office 2002. Drivers for ODBC MS Access is above 4.0
and Installshield Version is 5.5.

Please help me to resolve this Issue.

-Regards
Harpreet

The default value for both Jet 3.5 and 4.0 is 9500.

If your installation script is causing Jet to be re-registered it will reset the values in the registry back to their defaults and over write yours.

The 9500 value was originally put in for Netware servers and typically you do not need to change it from its default pf 9500.

See page 611 of "The Jet Database Engine Programmers Guide" or futher searching of MSDN.

|||

Hi Joel,

Thanx for your reply.

Could you please let me know from where this default value of 9500 is retrieved and set the registry variable.

Could you please get me access to "The Jet Database Engine Programmers Guide" . I currently do not have this guide.

-Regards

Harpreet

|||

Here is a link to the book on Amazon:

http://www.amazon.com/Microsoft-Database-Programmers-Professional-Editions/dp/B00005TNX9

The registry is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Jet 4.0\MaxLocksPerFile

default is 9500

|||

Hi Joel

Thanks for the information.

Still I have one question: Is there some file (configuration file or so) from where this default value of 9500 is taken and set in to the registry.

-Regards

Harpreet

|||The registry value is created in setup or when registering msjet40.dll.|||

HI Joel,

Can we change this registry value during registering.We have _drivers.ini file which contains default values for arguments.I tried to set the custom value in that ini file, but during installation, registry value is again set to default value of 9500.

MaxLocksPerFile

Hi

I wrote a script in Installshield that changes the MaxLocksPerFile value in
Registry for Jet 3.x and Jet 4.0
While installing the application through Installshield, the custom value for
MaxLocksPerFile is being overwritten to 9500 in Registry for Jet
4.0(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 4.0) but not
for Jet 3.x(HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Jet\4.0\Engines\Jet 3.x).
The value is being overwritten to 9500 before the control reaches at the
script code.

I am wondering from where this 9500 value is being retrieved and set in
Registry.
Is there some file where these default values are mentioned.
If so then why 9500 value is not being set for Jet 3.x and is being set only
for Jet 4.0.

i am using MS Office 2002. Drivers for ODBC MS Access is above 4.0
and Installshield Version is 5.5.

Please help me to resolve this Issue.

-Regards
Harpreet

The default value for both Jet 3.5 and 4.0 is 9500.

If your installation script is causing Jet to be re-registered it will reset the values in the registry back to their defaults and over write yours.

The 9500 value was originally put in for Netware servers and typically you do not need to change it from its default pf 9500.

See page 611 of "The Jet Database Engine Programmers Guide" or futher searching of MSDN.

|||

Hi Joel,

Thanx for your reply.

Could you please let me know from where this default value of 9500 is retrieved and set the registry variable.

Could you please get me access to "The Jet Database Engine Programmers Guide" . I currently do not have this guide.

-Regards

Harpreet

|||

Here is a link to the book on Amazon:

http://www.amazon.com/Microsoft-Database-Programmers-Professional-Editions/dp/B00005TNX9

The registry is:

HKEY_LOCAL_MACHINE\Software\Microsoft\Jet\4.0\Engines\Jet 4.0\MaxLocksPerFile

default is 9500

|||

Hi Joel

Thanks for the information.

Still I have one question: Is there some file (configuration file or so) from where this default value of 9500 is taken and set in to the registry.

-Regards

Harpreet

|||The registry value is created in setup or when registering msjet40.dll.|||

HI Joel,

Can we change this registry value during registering.We have _drivers.ini file which contains default values for arguments.I tried to set the custom value in that ini file, but during installation, registry value is again set to default value of 9500.

MaxInsertCommitSize - SQL Server Destination

Installing SP1 for SQL Server 2005 should get this property ? I am not able to get the same even after installing SP1

Can Anybody guide me here ?

This isn't an option on SQL Server destinations. Use the "Fast Load" option of OLE DB Destinations instead.|||Thanks for the comments Phil, so does this mean that there is no way I can specify a batch commit size. can i do some sort of error handling in SQL Server Destinaton ?|||

MShetty wrote:

Thanks for the comments Phil, so does this mean that there is no way I can specify a batch commit size. can i do some sort of error handling in SQL Server Destinaton ?

Using a SQL Server destination does not perform any error checking. It assumes that the data types are correct, keys will not be violated, etc... If you want to be able to redirect rows that fail on insert for one reason or another, use the OLE DB Destination instead. SQL Server destinations are designed to be super fast at the cost of data validation.

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