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 Upgrade

Please advice.
I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
2.6 SP1.
I would like to upgrade this to MDAC 2.7. Can I simply
run the MDAC 2.7 update or what is the Microsoft way to
do this.
Help Appreciated.SQL Server 2000 Service Pack 3a comes with MDAC 2.7 Service Pack 1a, so the
best way is to install the SQL Server Service Pack.
--
Jacco Schalkwijk
SQL Server MVP
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> Please advice.
> I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
> 2.6 SP1.
> I would like to upgrade this to MDAC 2.7. Can I simply
> run the MDAC 2.7 update or what is the Microsoft way to
> do this.
> Help Appreciated.|||MDAC 2.8 is also availabe for download from MS site.
Regards
Chip
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
>> Please advice.
>> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
MDAC
>> 2.6 SP1.
>> I would like to upgrade this to MDAC 2.7. Can I simply
>> run the MDAC 2.7 update or what is the Microsoft way to
>> do this.
>> Help Appreciated.
>
>.
>|||Thanks for your reply.
My configuration is WIN 2k SP3 plus SQL 2K Client tools
with MDAC 2.6 SP1. What is the best course of action to
upgrade to MDAC 2.7
Help Appreciated.
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
>> Please advice.
>> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
MDAC
>> 2.6 SP1.
>> I would like to upgrade this to MDAC 2.7. Can I simply
>> run the MDAC 2.7 update or what is the Microsoft way to
>> do this.
>> Help Appreciated.
>
>.
>|||Olutimi,
We run Win 2K SP4 and SQL2000 SP2 +. Remember to make sure that the server
MDAC is at least the same level as the client or higher. MDAC can introduce
changes that cause things like DTS, run from the client, to fail.
We upgraded the server to MDAC 2.7SP1A and then the clients. A simple
download and then run the DASETUP.
HTH
Chris Wood
Alberta Department of Energy
CANADA
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e17301c3f0b9$9ec87860$a301280a@.phx.gbl...
> Thanks for your reply.
> My configuration is WIN 2k SP3 plus SQL 2K Client tools
> with MDAC 2.6 SP1. What is the best course of action to
> upgrade to MDAC 2.7
> Help Appreciated.
>
> >--Original Message--
> >SQL Server 2000 Service Pack 3a comes with MDAC 2.7
> Service Pack 1a, so the
> >best way is to install the SQL Server Service Pack.
> >
> >--
> >Jacco Schalkwijk
> >SQL Server MVP
> >
> >
> >"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> >> Please advice.
> >>
> >> I have a WIN 2K SP3 ADV Server that runs SQL 2K with
> MDAC
> >> 2.6 SP1.
> >> I would like to upgrade this to MDAC 2.7. Can I simply
> >> run the MDAC 2.7 update or what is the Microsoft way to
> >> do this.
> >>
> >> Help Appreciated.
> >
> >
> >.
> >

MDAC Upgrade

Please advice.
I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
2.6 SP1.
I would like to upgrade this to MDAC 2.7. Can I simply
run the MDAC 2.7 update or what is the Microsoft way to
do this.
Help Appreciated.SQL Server 2000 Service Pack 3a comes with MDAC 2.7 Service Pack 1a, so the
best way is to install the SQL Server Service Pack.
Jacco Schalkwijk
SQL Server MVP
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
> Please advice.
> I have a WIN 2K SP3 ADV Server that runs SQL 2K with MDAC
> 2.6 SP1.
> I would like to upgrade this to MDAC 2.7. Can I simply
> run the MDAC 2.7 update or what is the Microsoft way to
> do this.
> Help Appreciated.|||MDAC 2.8 is also availabe for download from MS site.
Regards
Chip
>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
MDAC
>
>.
>|||Thanks for your reply.
My configuration is WIN 2k SP3 plus SQL 2K Client tools
with MDAC 2.6 SP1. What is the best course of action to
upgrade to MDAC 2.7
Help Appreciated.

>--Original Message--
>SQL Server 2000 Service Pack 3a comes with MDAC 2.7
Service Pack 1a, so the
>best way is to install the SQL Server Service Pack.
>--
>Jacco Schalkwijk
>SQL Server MVP
>
>"Olutimi" <anonymous@.discussions.microsoft.com> wrote in
message
>news:e9c601c3f096$369ceb40$a501280a@.phx.gbl...
MDAC
>
>.
>|||Olutimi,
We run Win 2K SP4 and SQL2000 SP2 +. Remember to make sure that the server
MDAC is at least the same level as the client or higher. MDAC can introduce
changes that cause things like DTS, run from the client, to fail.
We upgraded the server to MDAC 2.7SP1A and then the clients. A simple
download and then run the DASETUP.
HTH
Chris Wood
Alberta Department of Energy
CANADA
"Olutimi" <anonymous@.discussions.microsoft.com> wrote in message
news:e17301c3f0b9$9ec87860$a301280a@.phx.gbl...
> Thanks for your reply.
> My configuration is WIN 2k SP3 plus SQL 2K Client tools
> with MDAC 2.6 SP1. What is the best course of action to
> upgrade to MDAC 2.7
> Help Appreciated.
>
> Service Pack 1a, so the
> message
> MDAC

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

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 2.8 Install - any issues?

Hi all,
About to start a project to upgrade to MDAC 2.8 from MDAC 2.6 on a number of servers. Has anyone encountered any issues with this? Also, if we do NOT upgrade several client workstations, might we expect problems as a result?

We are aware that we need to patch MDAC for the vulnerability issues, but we are trying to comine this with a server upgrade for servers at risk. Has anyone had experience on a similar project?
Cheers,
DunNot so far, but you should be better off if you can carry the implementation on test environment.

Take a note from this KBA (http://support.microsoft.com/?kbid=828396) about MDAC 2.8.

HTH