MAX and DATEDIFF: version

Showing posts with label version. Show all posts

Friday, March 30, 2012

MDAC Version....

How to find out MDAC version on a given computer ?
Albert> Is it required to stay completely current with MDAC new
> releases?
Required by what, who? Really depends on your requirements...
Personally, since each new version has potential fixes and security patches,
so I try to stay as up-to-date as possible.
Of course, don't deploy to production until you test it in a similar
environment.

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 Version ?

How can I find out the version of MDAC ?
TIATry
http://support.microsoft.com/kb/231943
Or are you looking for something specific ?
Peter
"The United States has much to offer the third world war."
Ronald Reagan
"Kelly" wrote:

> How can I find out the version of MDAC ?
> TIA|||http://www.aspfaq.com/2057
http://www.aspfaq.com/
(Reverse address to reply.)
"Kelly" <Kelly@.discussions.microsoft.com> wrote in message
news:A19900B6-43D7-45E5-B7FE-6D0423EEF1FB@.microsoft.com...
> How can I find out the version of MDAC ?
> TIA

MDAC Version ?

How can I find out the version of MDAC ?
TIA
Try
http://support.microsoft.com/kb/231943
Or are you looking for something specific ?
Peter
"The United States has much to offer the third world war."
Ronald Reagan
"Kelly" wrote:

> How can I find out the version of MDAC ?
> TIA
|||http://www.aspfaq.com/2057
http://www.aspfaq.com/
(Reverse address to reply.)
"Kelly" <Kelly@.discussions.microsoft.com> wrote in message
news:A19900B6-43D7-45E5-B7FE-6D0423EEF1FB@.microsoft.com...
> How can I find out the version of MDAC ?
> TIA

MDAC Version ?

How can I find out the version of MDAC ?
TIATry
http://support.microsoft.com/kb/231943
Or are you looking for something specific ?
Peter
"The United States has much to offer the third world war."
Ronald Reagan
"Kelly" wrote:
> How can I find out the version of MDAC ?
> TIA|||http://www.aspfaq.com/2057
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Kelly" <Kelly@.discussions.microsoft.com> wrote in message
news:A19900B6-43D7-45E5-B7FE-6D0423EEF1FB@.microsoft.com...
> How can I find out the version of MDAC ?
> TIAsql

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

How do I determine the MDAC version SQL Server 2000 is using?
Thank You,Joe
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Joe P." <Joe P.@.discussions.microsoft.com> wrote in message
news:D6FEEB77-C960-4970-B716-DCF33137DD3D@.microsoft.com...
> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,
>|||Microsoft has a tool that will tell you which version is there and if
the files are current.
It is possible to have the MDAC stack corrupted and have the state of
things very confused!
Microsoft KB306132 addresses this issue.
TOOL:
http://www.microsoft.com/downloads/...en&Hash=NHX676C
Joe P. wrote:

> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,

Mdac version

Hi,
How do I check the version of Mdac in sql box?
Thankshttp://support.microsoft.com/default.aspx?kbid=301202#3
Check the Version Information Stored in the Registry
Although not the most reliable way to check the MDAC version, checking the
registry for the version information is an easy way to double-check this
information (if you are not experiencing any MDAC-related issues).
The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\Da
taAccess\FullInstallVer
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I check the version of Mdac in sql box?
> Thanks
>|||use a tool from MS called ComChecker...
http://www.microsoft.com/downloads/...&displaylang=en
"mecn" <mecn2002@.yahoo.com> wrote in message
news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I check the version of Mdac in sql box?
> Thanks
>|||thanks all
Works on both
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23CiWbmfbGHA.3352@.TK2MSFTNGP03.phx.gbl...
> http://support.microsoft.com/default.aspx?kbid=301202#3
> Check the Version Information Stored in the Registry
> Although not the most reliable way to check the MDAC version, checking the
> registry for the version information is an easy way to double-check this
> information (if you are not experiencing any MDAC-related issues).
> The version information is found in the following key:
> HKEY_LOCAL_MACHINE\Software\Microsoft\Da
taAccess\FullInstallVer
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
>

MDAC Version

How do I determine the MDAC version SQL Server 2000 is using?
Thank You,
Joe
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Joe P." <Joe P.@.discussions.microsoft.com> wrote in message
news:D6FEEB77-C960-4970-B716-DCF33137DD3D@.microsoft.com...
> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,
>
|||Microsoft has a tool that will tell you which version is there and if
the files are current.
It is possible to have the MDAC stack corrupted and have the state of
things very confused!
Microsoft KB306132 addresses this issue.
TOOL:
http://www.microsoft.com/downloads/d...n&Hash=NHX676C
Joe P. wrote:

> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,
sql

MDAC version

Hi!
How to know which version of MDAC I currently use?
Thanks.
Dmitry| Hi!
|
| How to know which version of MDAC I currently use?
|
| Thanks.
|
| Dmitry
--
Hi Dmitry,
Please refer to this Technet article:
HOW TO: Check for MDAC version
http://support.microsoft.com/?id=301202
Hope this helps,
--
Eric Cárdenas
SQL Server support|||There is an MDAC version checker that can be got from MS web site
"Dmitry Karneyev" <karneyev@.msn.com> wrote in message
news:%23hzhvc7vDHA.2000@.TK2MSFTNGP11.phx.gbl...
> Hi!
> How to know which version of MDAC I currently use?
> Thanks.
> Dmitry
>

MDAC Version

How do I determine the MDAC version SQL Server 2000 is using?
Thank You,Joe
EXEC master..xp_regread
N'HKEY_LOCAL_MACHINE',
N'Software\Microsoft\DataAccess',
N'Version'
"Joe P." <Joe P.@.discussions.microsoft.com> wrote in message
news:D6FEEB77-C960-4970-B716-DCF33137DD3D@.microsoft.com...
> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,
>|||Microsoft has a tool that will tell you which version is there and if
the files are current.
It is possible to have the MDAC stack corrupted and have the state of
things very confused!
Microsoft KB306132 addresses this issue.
TOOL:
http://www.microsoft.com/downloads/details.aspx?FamilyID=8f0a8df6-4a21-4b43-bf53-14332ef092c9&displaylang=en&Hash=NHX676C
Joe P. wrote:
> How do I determine the MDAC version SQL Server 2000 is using?
> Thank You,

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 version

Hi,
How do I check the version of Mdac in sql box?
Thanksuse a tool from MS called ComChecker...
http://www.microsoft.com/downloads/details.aspx?FamilyId=8F0A8DF6-4A21-4B43-BF53-14332EF092C9&displaylang=en
"mecn" <mecn2002@.yahoo.com> wrote in message
news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I check the version of Mdac in sql box?
> Thanks
>|||http://support.microsoft.com/default.aspx?kbid=301202#3
Check the Version Information Stored in the Registry
Although not the most reliable way to check the MDAC version, checking the
registry for the version information is an easy way to double-check this
information (if you are not experiencing any MDAC-related issues).
The version information is found in the following key:
HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
> Hi,
> How do I check the version of Mdac in sql box?
> Thanks
>|||thanks all
Works on both
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23CiWbmfbGHA.3352@.TK2MSFTNGP03.phx.gbl...
> http://support.microsoft.com/default.aspx?kbid=301202#3
> Check the Version Information Stored in the Registry
> Although not the most reliable way to check the MDAC version, checking the
> registry for the version information is an easy way to double-check this
> information (if you are not experiencing any MDAC-related issues).
> The version information is found in the following key:
> HKEY_LOCAL_MACHINE\Software\Microsoft\DataAccess\FullInstallVer
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:u7Nr5hfbGHA.1208@.TK2MSFTNGP02.phx.gbl...
>> Hi,
>> How do I check the version of Mdac in sql box?
>> Thanks
>sql

MDAC Madness

Wednesday, March 28, 2012

MDAC Madness

Greetings,
On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
server? Very confusing. Will someone help me get my head around this?
Further, when I set the Component Checker to perform analysis against a
selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
8.50.2162.0 is expected. Is this also anything to be concerned about?
Thanks,
Tim ==Tim,
You don't mention the level of SQL2000 that you are running? Is it SP4?
Chris Wood
<tim@.tcsys.com> wrote in message
news:1123081469.455549.23850@.f14g2000cwb.googlegroups.com...
> Greetings,
> On my Windows 2000 SP4 Server, the MDAC Component Checker Version 2.0
> reports that MDAC 2.8 SP1 on Windows XP SP2 is installed.
> MDAC 2.8 SP1 on Windows XP SP2 ... but this is a Windows 2000 SP4
> server? Very confusing. Will someone help me get my head around this?
> Further, when I set the Component Checker to perform analysis against a
> selected version, and target MDAC 2.8 SP1 on Windows XP SP2, only one
> inconsistency is reported -- msxml3.dll is at version 8.70.1104.0, but
> 8.50.2162.0 is expected. Is this also anything to be concerned about?
> Thanks,
> Tim ==>|||Thanks for replying, Chris.
I know almost nothing about SQL server, but, that being said, I'm an
otherwise competent MS net admin.
This particular box has an MSDE engine installed by an not-profit
financial application. The management of this app is hands-off, under
the control of the vendor.
The thing is, the same server is also our Backup Exec box. Backup Exec
was configured to use the same SQL instance as the financial app.
That's not unusual; the use of an existing SQL or MSDE instance on the
same box is the default installation setting for Backup Exec.
But lately we've been having some trouble with Backup Exec. And
wouldn't you know it? Some mismatched MDAC files turned up in the
course of investigation, and now Veritas/Symantec technical support is
insisting upon having the information in the OP before proceeding
further with the case.
So to answer your question: Knowing that this is an MSDE installation,
I was able to Google up this command line...
osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
...but I'm prompted for a password which I do not believe that I
posses.
I've tried running it with the local administrator account and the
domain administrator account. No luck.
Believe me, your continued assistance is appreciated!|||Tim,
If you are using an Windows administrator id I think that use can use the -E
rather than -U parameter. This should not ask for a password.
From the MSDE SP4 readme
1.5 Verify the Version of Microsoft Data Access Components
MSDE 2000 SP4 setup determines whether to upgrade an installed version of
Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
obtain MDAC 2.8 SP2.
c.. MDAC 2.8 SP1 is not installed on computers that already have installed
an equal or later version of MDAC.
d..
e.. 1.6 Identify the Current Version of MSDE 2000
Before running Setup, identify the version of the MSDE 2000 instance that
is being upgraded. If the version of MSDE 2000 is already at or greater than
SP4, you do not need to install SP4.
To identify the installed version of MSDE 2000:
1.. Execute one of the following queries against an instance of the
database engine by using isql, osql, or Query Analyzer.
a.. SELECT SERVERPROPERTY('ProductLevel')
b.. SELECT @.@.VERSION
c.. SELECT SERVERPROPERTY('ProductVersion')
2.. Find out your version of MSDE by means of the following table. SQL
Server 2000 Version and Level @.@.VERSION Product Level
SQL Server 2000 Original Release 8.00.194 RTM
Desktop Engine SP1 8.00.384 SP1
Desktop Engine SP2 8.00.534 SP2
Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
MSDE 2000 SP4 8.00.2039 SP4
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Tim,
Did you find out the build of MSDE?
Chris
<tim@.tcsys.com> wrote in message
news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> Thanks for replying, Chris.
> I know almost nothing about SQL server, but, that being said, I'm an
> otherwise competent MS net admin.
> This particular box has an MSDE engine installed by an not-profit
> financial application. The management of this app is hands-off, under
> the control of the vendor.
> The thing is, the same server is also our Backup Exec box. Backup Exec
> was configured to use the same SQL instance as the financial app.
> That's not unusual; the use of an existing SQL or MSDE instance on the
> same box is the default installation setting for Backup Exec.
> But lately we've been having some trouble with Backup Exec. And
> wouldn't you know it? Some mismatched MDAC files turned up in the
> course of investigation, and now Veritas/Symantec technical support is
> insisting upon having the information in the OP before proceeding
> further with the case.
> So to answer your question: Knowing that this is an MSDE installation,
> I was able to Google up this command line...
> osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> ...but I'm prompted for a password which I do not believe that I
> posses.
> I've tried running it with the local administrator account and the
> domain administrator account. No luck.
> Believe me, your continued assistance is appreciated!
>|||Chris,
This thread speaks to a problem I created on our SBS 2003 with MDAC now
having 5 mismatched file versions and a crippled Veritas BackupExec 10, not
to mention the other problems this MDAC issue is causing. I lost RAS
yesterday (related? who knows!) and I can no longer access our Exchange
Server through the Web access for Outlook 2003.
I really messed things up and need help to get the correct MDAC files
restored. I used the cc.exe. Component Checker from MS to test the installed
version against the expected file versions.
Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
HELP!
Chris
"Chris Wood" wrote:
> Tim,
> If you are using an Windows administrator id I think that use can use the -E
> rather than -U parameter. This should not ask for a password.
> From the MSDE SP4 readme
> 1.5 Verify the Version of Microsoft Data Access Components
> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>
> b.. Computers that run Windows XP or Windows Server 2003 are not upgraded
> to MDAC 2.8 SP1. If your system requires any of the fixes included in MDAC
> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1 to
> obtain MDAC 2.8 SP2.
>
> c.. MDAC 2.8 SP1 is not installed on computers that already have installed
> an equal or later version of MDAC.
> d..
> e.. 1.6 Identify the Current Version of MSDE 2000
> Before running Setup, identify the version of the MSDE 2000 instance that
> is being upgraded. If the version of MSDE 2000 is already at or greater than
> SP4, you do not need to install SP4.
> To identify the installed version of MSDE 2000:
> 1.. Execute one of the following queries against an instance of the
> database engine by using isql, osql, or Query Analyzer.
> a.. SELECT SERVERPROPERTY('ProductLevel')
>
> b.. SELECT @.@.VERSION
>
> c.. SELECT SERVERPROPERTY('ProductVersion')
> 2.. Find out your version of MSDE by means of the following table. SQL
> Server 2000 Version and Level @.@.VERSION Product Level
> SQL Server 2000 Original Release 8.00.194 RTM
> Desktop Engine SP1 8.00.384 SP1
> Desktop Engine SP2 8.00.534 SP2
> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> MSDE 2000 SP4 8.00.2039 SP4
> Chris
> <tim@.tcsys.com> wrote in message
> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> > Thanks for replying, Chris.
> >
> > I know almost nothing about SQL server, but, that being said, I'm an
> > otherwise competent MS net admin.
> >
> > This particular box has an MSDE engine installed by an not-profit
> > financial application. The management of this app is hands-off, under
> > the control of the vendor.
> >
> > The thing is, the same server is also our Backup Exec box. Backup Exec
> > was configured to use the same SQL instance as the financial app.
> > That's not unusual; the use of an existing SQL or MSDE instance on the
> > same box is the default installation setting for Backup Exec.
> >
> > But lately we've been having some trouble with Backup Exec. And
> > wouldn't you know it? Some mismatched MDAC files turned up in the
> > course of investigation, and now Veritas/Symantec technical support is
> > insisting upon having the information in the OP before proceeding
> > further with the case.
> >
> > So to answer your question: Knowing that this is an MSDE installation,
> > I was able to Google up this command line...
> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> > ...but I'm prompted for a password which I do not believe that I
> > posses.
> >
> > I've tried running it with the local administrator account and the
> > domain administrator account. No luck.
> >
> > Believe me, your continued assistance is appreciated!
> >
>
>|||Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
the Premium edition that includes full blown SQL2000 SP4.
If this is SP1 then my previous note about MDAC applies.
Chris
"Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
> Chris,
> This thread speaks to a problem I created on our SBS 2003 with MDAC now
> having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> not
> to mention the other problems this MDAC issue is causing. I lost RAS
> yesterday (related? who knows!) and I can no longer access our Exchange
> Server through the Web access for Outlook 2003.
> I really messed things up and need help to get the correct MDAC files
> restored. I used the cc.exe. Component Checker from MS to test the
> installed
> version against the expected file versions.
> Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> HELP!
> Chris
> "Chris Wood" wrote:
>> Tim,
>> If you are using an Windows administrator id I think that use can use
>> the -E
>> rather than -U parameter. This should not ask for a password.
>> From the MSDE SP4 readme
>> 1.5 Verify the Version of Microsoft Data Access Components
>> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
>> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
>> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
>>
>> b.. Computers that run Windows XP or Windows Server 2003 are not
>> upgraded
>> to MDAC 2.8 SP1. If your system requires any of the fixes included in
>> MDAC
>> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1
>> to
>> obtain MDAC 2.8 SP2.
>>
>> c.. MDAC 2.8 SP1 is not installed on computers that already have
>> installed
>> an equal or later version of MDAC.
>> d..
>> e.. 1.6 Identify the Current Version of MSDE 2000
>> Before running Setup, identify the version of the MSDE 2000 instance
>> that
>> is being upgraded. If the version of MSDE 2000 is already at or greater
>> than
>> SP4, you do not need to install SP4.
>> To identify the installed version of MSDE 2000:
>> 1.. Execute one of the following queries against an instance of the
>> database engine by using isql, osql, or Query Analyzer.
>> a.. SELECT SERVERPROPERTY('ProductLevel')
>>
>> b.. SELECT @.@.VERSION
>>
>> c.. SELECT SERVERPROPERTY('ProductVersion')
>> 2.. Find out your version of MSDE by means of the following table.
>> SQL
>> Server 2000 Version and Level @.@.VERSION Product Level
>> SQL Server 2000 Original Release 8.00.194 RTM
>> Desktop Engine SP1 8.00.384 SP1
>> Desktop Engine SP2 8.00.534 SP2
>> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
>> MSDE 2000 SP4 8.00.2039 SP4
>> Chris
>> <tim@.tcsys.com> wrote in message
>> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
>> > Thanks for replying, Chris.
>> >
>> > I know almost nothing about SQL server, but, that being said, I'm an
>> > otherwise competent MS net admin.
>> >
>> > This particular box has an MSDE engine installed by an not-profit
>> > financial application. The management of this app is hands-off, under
>> > the control of the vendor.
>> >
>> > The thing is, the same server is also our Backup Exec box. Backup Exec
>> > was configured to use the same SQL instance as the financial app.
>> > That's not unusual; the use of an existing SQL or MSDE instance on the
>> > same box is the default installation setting for Backup Exec.
>> >
>> > But lately we've been having some trouble with Backup Exec. And
>> > wouldn't you know it? Some mismatched MDAC files turned up in the
>> > course of investigation, and now Veritas/Symantec technical support is
>> > insisting upon having the information in the OP before proceeding
>> > further with the case.
>> >
>> > So to answer your question: Knowing that this is an MSDE installation,
>> > I was able to Google up this command line...
>> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
>> > ...but I'm prompted for a password which I do not believe that I
>> > posses.
>> >
>> > I've tried running it with the local administrator account and the
>> > domain administrator account. No luck.
>> >
>> > Believe me, your continued assistance is appreciated!
>> >
>>|||Chris (Wood),
Are you asking about my server issue or the one from Tim? We are not at SP1
for our SBS 2003 yet because the server would not allow Windows Update to
properly run much less update it's components. I have all 5 of the Microsoft
specified downloads for SBS 2003 SP1 downloaded as per an article I read on
the SBS MS site. I was planning to do some more reading on this before trying
to apply them and was hoping that would fix my browser issue that kept it
from running Windows Update properly.
Frankly this server was a walking abortion from the get go with the company
that originally installed it doing a very poor job. I band-aided everything I
could safely do to even get it to run without daily unexpected re-boots. I
know that was putting off the inevidable, but the company needed to get back
to daily operations after 30+ days of dissruption caused by this "other"
outside computer company. We have since severed ties with them.
Anyway, we are running with only the original installation of SBS 2003, some
security patches in place and not much else. I also wanted to update the
exchange server to SP1 (this is part of the process I hope to complete once I
fix my MDAC issues).
Since I last posted, I tossed in my towel on this and have a engineer coming
in this morning from a group that has been trying to get our business for
some time now. I hope he will know what to do to fix this MDAC problem.
But any input you can offer will be good. Also, we are running the standard
version of SBS 2003, not the premium, thus the SQL is only that MSDE2000,
which I am growing to hate by the minute. I would have ponyed up the money
for the premium if I where actually working here when they were forced to get
a new server back in December 2004. (The old server was a Netware server that
this same outside computer company supported, broke and then said it's better
to scrap that server and replace it with the SBS 2003 they installed - This
Machine. We all know how well a job they did on that too!)
Sorry to rant. It's been a long week and I am stressed out.
Chris W.
"Chris Wood" wrote:
> Is this SBS 2003 SP1? It looks like it includes MSDE2000 SP4 unless you have
> the Premium edition that includes full blown SQL2000 SP4.
> If this is SP1 then my previous note about MDAC applies.
> Chris
> "Chris Williams" <Chris Williams@.discussions.microsoft.com> wrote in message
> news:BE841E75-8D2C-4EE1-B2E7-D4BE9EAD417E@.microsoft.com...
> > Chris,
> >
> > This thread speaks to a problem I created on our SBS 2003 with MDAC now
> > having 5 mismatched file versions and a crippled Veritas BackupExec 10,
> > not
> > to mention the other problems this MDAC issue is causing. I lost RAS
> > yesterday (related? who knows!) and I can no longer access our Exchange
> > Server through the Web access for Outlook 2003.
> >
> > I really messed things up and need help to get the correct MDAC files
> > restored. I used the cc.exe. Component Checker from MS to test the
> > installed
> > version against the expected file versions.
> >
> > Veritas/Symantec will not proceed with assistance until I get MDAC fixed.
> >
> > HELP!
> >
> > Chris
> >
> > "Chris Wood" wrote:
> >
> >> Tim,
> >>
> >> If you are using an Windows administrator id I think that use can use
> >> the -E
> >> rather than -U parameter. This should not ask for a password.
> >>
> >> From the MSDE SP4 readme
> >>
> >> 1.5 Verify the Version of Microsoft Data Access Components
> >> MSDE 2000 SP4 setup determines whether to upgrade an installed version of
> >> Microsoft Data Access Components (MDAC) to MDAC 2.8 SP1:
> >>
> >> a.. Computers that run Windows 2000 are upgraded to MDAC 2.8 SP1.
> >>
> >>
> >> b.. Computers that run Windows XP or Windows Server 2003 are not
> >> upgraded
> >> to MDAC 2.8 SP1. If your system requires any of the fixes included in
> >> MDAC
> >> 2.8 SP1, upgrade your system to Windows XP SP2 or Windows Server 2003 SP1
> >> to
> >> obtain MDAC 2.8 SP2.
> >>
> >>
> >> c.. MDAC 2.8 SP1 is not installed on computers that already have
> >> installed
> >> an equal or later version of MDAC.
> >> d..
> >> e.. 1.6 Identify the Current Version of MSDE 2000
> >> Before running Setup, identify the version of the MSDE 2000 instance
> >> that
> >> is being upgraded. If the version of MSDE 2000 is already at or greater
> >> than
> >> SP4, you do not need to install SP4.
> >>
> >> To identify the installed version of MSDE 2000:
> >>
> >> 1.. Execute one of the following queries against an instance of the
> >> database engine by using isql, osql, or Query Analyzer.
> >> a.. SELECT SERVERPROPERTY('ProductLevel')
> >>
> >>
> >> b.. SELECT @.@.VERSION
> >>
> >>
> >> c.. SELECT SERVERPROPERTY('ProductVersion')
> >> 2.. Find out your version of MSDE by means of the following table.
> >> SQL
> >> Server 2000 Version and Level @.@.VERSION Product Level
> >> SQL Server 2000 Original Release 8.00.194 RTM
> >> Desktop Engine SP1 8.00.384 SP1
> >> Desktop Engine SP2 8.00.534 SP2
> >> Desktop Engine SP3, SP3a, or MSDE 2000 Release A. 8.00.760 SP3
> >> MSDE 2000 SP4 8.00.2039 SP4
> >>
> >> Chris
> >> <tim@.tcsys.com> wrote in message
> >> news:1123100308.823774.310400@.g49g2000cwa.googlegroups.com...
> >> > Thanks for replying, Chris.
> >> >
> >> > I know almost nothing about SQL server, but, that being said, I'm an
> >> > otherwise competent MS net admin.
> >> >
> >> > This particular box has an MSDE engine installed by an not-profit
> >> > financial application. The management of this app is hands-off, under
> >> > the control of the vendor.
> >> >
> >> > The thing is, the same server is also our Backup Exec box. Backup Exec
> >> > was configured to use the same SQL instance as the financial app.
> >> > That's not unusual; the use of an existing SQL or MSDE instance on the
> >> > same box is the default installation setting for Backup Exec.
> >> >
> >> > But lately we've been having some trouble with Backup Exec. And
> >> > wouldn't you know it? Some mismatched MDAC files turned up in the
> >> > course of investigation, and now Veritas/Symantec technical support is
> >> > insisting upon having the information in the OP before proceeding
> >> > further with the case.
> >> >
> >> > So to answer your question: Knowing that this is an MSDE installation,
> >> > I was able to Google up this command line...
> >> > osql.exe -U administrator -Q "USE master SELECT @.@.version" -p
> >> > ...but I'm prompted for a password which I do not believe that I
> >> > posses.
> >> >
> >> > I've tried running it with the local administrator account and the
> >> > domain administrator account. No luck.
> >> >
> >> > Believe me, your continued assistance is appreciated!
> >> >
> >>
> >>
> >>
>
>sql

MDAC and SQL Server 2005

In the SQL Server 2005 upgrade advisor help file it states the following...

"Upgrade Advisor detected an older version of MDAC. MDAC versions before MDAC 2.8 SP1 do not support named instances. To allow application connections to named instances, upgrade to MDAC 2.8 SP1."

I've installed our application which uses ADO (not ADO.NET) to connect to an SQL Server named instance on a client machine. Our application installs MDAC 2.6. Therefore on older machines such as Windows 95 MDAC is upgraded to 2.6. Our application can still connect to the named instance without MDAC 2.8 SP1 being present.

Is this statement in the upgrade advisor entirely true or am I misunderstanding what it means?

Thanks.MDAC 2.6 does support named instances. However, SQL Server 2005 requires MDAC 2.8SP1 or higher

Hope this helps.

Regards
Uwa|||Thanks for the reply. When you say SQL Server 2005 requires MDAC 2.8SP1 or higher, do you mean being able to use SQL Server itself on the machine it is installed on or do you mean 2.8SP1 is required by clients for connectivity.

I've got a client machine here with MDAC 2.6SP2 installed where our application can perfectly connect to my server which is running SQL Server 2005 in a named instance.

Thanks|||SQL Server 2005 requires MDAC 28SP1 or higher on the machine it's installed on. Client machines with any MDAC version can connect to it but with some possible limitations (for example there is no support for named instances prior to MDAC 26).

For better performance and if you use the new data types in SQL Server 2005 or other cool new features (MARS, notifications etc), I would recommend you use the new SQLNCLI (SQL Server native client) which has the equivalent of the OLEDB provider and ODBC Driver in one DLL package. It has it's own MSI installer that is on the Server media. Please see http://support.microsoft.com/?kbid=910016 for more info|||Thanks for the information. My main concern is getting our existing applications that are based on SQL Server 2000 working with SQL Server 2005 so I am just concerned about MDAC at the moment.

I will certainly check out SQLNCLI though as that sounds interesting.

Thanks|||SQL Native Client is a good choice if you are using new features in SQL Server 2005. It's peformance is likely to be better than MDAC in many cases and it also scales better on multiprocessor machines.

However, if you have deployed clients and you are simply upgrading the server to SQL Server 2005 there is no requirement to upgrade from MDAC to SQL Native Client.|||

Thanks guys for good info.

I have a similar question. We have an application (C++ and built in 32bit) using ODBC driver to connec to SQL Server 2000 or Oracle 9 server. Can our application connect to SQL Server 2005 (64bit) without modification? We dont mind to install MDAC 2.8SP1 on the SQL Server 2005 (64bit) machine.

I would appreciate your help.

John

|||

ODBC connectivity to SQL Server 2005 on 64bit is supported either via MDAC or the new SQL Native Client ODBC driver (which offers better performance and features in some areas).

And by the way, MDAC 28 is part of the Windows 2003 and XP operating systems so you will not need to install this.

Hope this helps.

Uwa

MDAC and SQL Server 2005

In the SQL Server 2005 upgrade advisor help file it states the following...

"Upgrade Advisor detected an older version of MDAC. MDAC versions before MDAC 2.8 SP1 do not support named instances. To allow application connections to named instances, upgrade to MDAC 2.8 SP1."

Is this statement in the upgrade advisor entirely true or am I misunderstanding what it means?

Thanks.MDAC 2.6 does support named instances. However, SQL Server 2005 requires MDAC 2.8SP1 or higher

Hope this helps.

I've got a client machine here with MDAC 2.6SP2 installed where our application can perfectly connect to my server which is running SQL Server 2005 in a named instance.

I will certainly check out SQLNCLI though as that sounds interesting.

However, if you have deployed clients and you are simply upgrading the server to SQL Server 2005 there is no requirement to upgrade from MDAC to SQL Native Client.|||

Thanks guys for good info.

I would appreciate your help.

John

|||

ODBC connectivity to SQL Server 2005 on 64bit is supported either via MDAC or the new SQL Native Client ODBC driver (which offers better performance and features in some areas).

And by the way, MDAC 28 is part of the Windows 2003 and XP operating systems so you will not need to install this.

Hope this helps.

Uwa

Friday, March 30, 2012

MDAC Version....

MDAC version error

MDAC Version ?

MDAC Version ?

MDAC Version ?

MDAC version

MDAC version

MDAC Version

Mdac version

MDAC Version

MDAC version

MDAC version

MDAC Version

MDAC version

Mdac version

MDAC Madness

MDAC Madness

Wednesday, March 28, 2012

MDAC Madness

MDAC and SQL Server 2005

MDAC and SQL Server 2005

MAX and DATEDIFF

Blog Archive

About Me