<div>
Q1: what you are seiing is security updates. MDAC is included in 2003<br />
Q2: Yes<br />
Q3: Partly. MDAC is included in XP and 2003 - so should be there regardless. Some elements of a SQL Server Environment &nbsp;might use those data access methods in say linked servers. But SQL Server itself is a complete install, and will include whatever it needs to function as a database server.<br />
Q4: Partly. Newer versions can handle older environments, but then you have things like 64 bit, Vista etc which does require the &quot;appropriate&quot; version. Some of the releases and upgrades are so it can manage those other versions, or, newer facilities. There are a few more implication from a developer perspective - e.g. trying to release an earlier MDAC version to a windows 2003 machine (which already has 2.8 included).<br />
<br />
you can get the latest (and there is an additional link down the bottom) from MSDN : <a href="http://msdn.microsoft.com/en-us/data/aa937730.aspx" rel="ugc">http://msdn.microsoft.com/en-us/data/aa937730.aspx</a><br />
<br />
and a brief overview of the release strategy : <a href="http://support.microsoft.com/kb/892854" rel="ugc nofollow">http://support.microsoft.com/kb/892854</a><br />
<br />
Interesting questions - what seems to be the problem ?
</div>


<div>
Hi Mark,<br />
<br />
Thanks for your excellent input. <br />
<br />
Background<br />
==========<br />
<br />
I migrated the SQL server 2000 database from old server (windows 2000 SE SP4) to new server (windows 2003 EE SP2). After the migration taken place, one of the applications cannot perform its activity.<br />
<br />
This application calls a batch script and it executes isql command. Before the database migration takes place, the batch scripts always completes succesfully, however after the migration taken place, it returns errors as follow:<br />
DB-Library: Unable to connect: SQL Server is unavailable or does not exist.<br />
Net-Library error 1326: ConnectionOpen (CreateFile()).<br />
<br />
I tried to execute the isql from the command line using the same user id and password, however I manage to connect to the new database server succesfully. (Note. I open a question regarding &quot;How to do the debugging on the dos prompt?&quot; on 17 July'08. My objective is to identify the SQL user id and password that is being used by the application)<br />
<br />
Initially, I thought is the MDAC version. Because the MDAC version on the application server is MDAC 2.5 and on the new database server is MDAC 2.8). Based on your input, I can rest assured that the MDAC is not the issue here.<br />
<br />
Now I'm puzzled, what will be the caused??????<br />

</div>


<div>
I'll follow your suggestions and thanks a lot for your input. If I still encounter problem, I'll open a new question and hopefully we'll meet again.
</div>


<div>
<div class="content wysiwyg-content">
(Q1)<br />
We just installed Windows 2003 SP2 on the database server and I just realized that I couldn't find MDAC program in Add/Remove Program. The old database server is installed with Windows 2000 SP4 and the MDAC program exists in the Add/Remove Program. Is it okay?<br />
<br />
(Q2)<br />
I've installed component checker on the new database server (with Windows 2003 EE SP2) and it returns UNKNOWN. Then I checked the windows registry (\HKLM\SOFTWARE\Microsoft\<wbr />DataAccess<wbr />\FullInsta<wbr />llVer), it shows 2.82.3959.0. I assume MDAC 2.8 has been installed on the new database. Am I correct?<br />
<br />
(Q3)<br />
Assuming the MDAC does not exist on the new database server (with Windows 2003 EE SP2), it is not required to install MDAC on the database server since SQL server does not require MDAC to perform its function. MDAC is only required to be installed on the client's workstation. Am I correct?<br />
<br />
(Q4)<br />
MDAC is part of O/S installation and meaning to say that its version depends on the O/S version. Am I correct?<br />
<br />
<a href="https://filedb.experts-exchange.com/incoming/2008/07_w29/42801/MDAC-queries.doc" target="_blank" class="file-inline" title="MDAC & compcheck snapshot (115 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>MDAC-queries.doc</a>
</div>
</div>


MDAC-queries.doc

(Q1)
We just installed Windows 2003 SP2 on the database server and I just realized that I couldn't find MDAC program in Add/Remove Program. The old database server is installed with Windows 2000 SP4 and the MDAC program exists in the Add/Remove Program. Is it okay?

(Q2)
I've installed component checker on the new database server (with Windows 2003 EE SP2) and it returns UNKNOWN. Then I checked the windows registry (\HKLM\SOFTWARE\Microsoft\DataAccess\FullInstallVer), it shows 2.82.3959.0. I assume MDAC 2.8 has been installed on the new database. Am I correct?

(Q3)
Assuming the MDAC does not exist on the new database server (with Windows 2003 EE SP2), it is not required to install MDAC on the database server since SQL server does not require MDAC to perform its function. MDAC is only required to be installed on the client's workstation. Am I correct?

(Q4)
MDAC is part of O/S installation and meaning to say that its version depends on the O/S version. Am I correct?


Queries on MDAC

The Microsoft Server topic includes all of the legacy versions of the operating system, including the Windows NT 3.1, NT 3.5, NT 4.0 and Windows 2000 and Windows Home Server versions.

Microsoft Server OS

Windows Server 2003 was based on Windows XP and was released in four editions: Web, Standard, Enterprise and Datacenter. It also had derivative versions for clusters, storage and Microsoft’s Small Business Server. Important upgrades included integrating Internet Information Services (IIS), improvements to Active Directory (AD) and Group Policy (GP), and the migration to Automated System Recovery (ASR).

Windows Server 2003

Databases are organized collections of data, most commonly accessed through management systems including schemas, tables, queries and processes that allow users to enter and manipulate the information or utilize it in other fashions, such as with web applications or for reporting purposes.