qwert85103
Technical User
Is MDAC 2.6 needed to connect to SQL Server thru ODBC?
Thanks.
Thanks.
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Is MDAC 2.6 needed to connect to SQL Server thru ODBC? 2
- Thread starter qwert85103
- Start date
- Status
-
1
- #2
It depends on what "connecting" means but in general no.
You should be able to go into your ODBC connections and set one up that connects no matter what MDAC you have installed.
Some application that then tries to use that connection might require a certain version....
You should be able to go into your ODBC connections and set one up that connects no matter what MDAC you have installed.
Some application that then tries to use that connection might require a certain version....
-
1
- #3
Hi,
MDAC versions 2.5 and earlier cannot connect to a named instance (virtual server) of SQL Server 2000. 2.6 is needed if you plan on referencing a named instance (virtual server). Although if you cannot upgrade to 2.6, you can still create an alias via the Client Network Utility.
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
MDAC versions 2.5 and earlier cannot connect to a named instance (virtual server) of SQL Server 2000. 2.6 is needed if you plan on referencing a named instance (virtual server). Although if you cannot upgrade to 2.6, you can still create an alias via the Client Network Utility.
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
- Thread starter
- #4
qwert85103
Technical User
JoeSack,
Could you please explain a little bit more as to how ceating an alias would solve the problem? I mean in logical terms for better understanding the idea.
Thanks.
Could you please explain a little bit more as to how ceating an alias would solve the problem? I mean in logical terms for better understanding the idea.
Thanks.
Sure,
If you have a SQL Server installation set up with a Named Instance on it, an example of it's name would be "ServerA\Instance1". A default instance of SQL Server would just be named "ServerA".
If your MDAC is pre-2.6, you would not be able to connect to the named instance using a name like "ServerA\Instance1".
If you did not have the option of upgrading to 2.6, and you are calling the Named Instance from a client with the SQL Server toolset loaded, you could set up an alias for the named instance.
Here is an article discussing exactly how to do this:
INF: How to Connect to an SQL Server 2000 Named Instance with the Previous Version's Client Tools
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
If you have a SQL Server installation set up with a Named Instance on it, an example of it's name would be "ServerA\Instance1". A default instance of SQL Server would just be named "ServerA".
If your MDAC is pre-2.6, you would not be able to connect to the named instance using a name like "ServerA\Instance1".
If you did not have the option of upgrading to 2.6, and you are calling the Named Instance from a client with the SQL Server toolset loaded, you could set up an alias for the named instance.
Here is an article discussing exactly how to do this:
INF: How to Connect to an SQL Server 2000 Named Instance with the Previous Version's Client Tools
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
I haven't set up any Virtual Servers but what exactly isn't working?
If you add an ODBC connection, select SQL Server Driver and put in either the name (or IP address if the servers name isn't resolving) valid user/pwd and make sure client configuration is TCP/IP what happens?
If you add an ODBC connection, select SQL Server Driver and put in either the name (or IP address if the servers name isn't resolving) valid user/pwd and make sure client configuration is TCP/IP what happens?
With regards to your original question, MDAC 2.6 is not necessary for an ODBC connection to a non-Virtual Server instance. So based on your situation, sounds like you should be okay.
What error are you getting when you set up the ODBC connection?
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
What error are you getting when you set up the ODBC connection?
Best Regards,
Joseph Sack, Author of "SQL Server 2000 Fast Answers for DBAs and Developers".
- Status
Similar threads
- Question
