| Groups | Blog | Home |
sql server clients : what does the SQL Server Client Tools (Client Connectivity Only) install option do?
libraries. Most applications only need MDAC. Generally you will only need MDAC which is already on most PC so the client connectivity install is usually not required. -Sue [quoted text, click to view] On Wed, 30 Mar 2005 18:38:32 +0800, <arch> wrote:
>I was under the impression that the Client Connectivity install was required >for every machine on a LAN network that wanted to connect via OLEDB to an >sql server database. However, I recently created an adp project in MS >Access that seemed to connect without any problems, even though the Client >Connectivity component wasn't installed. I am now confused exactly what >that install option actually does. Can someone give me a clue? > >
I was under the impression that the Client Connectivity install was required
for every machine on a LAN network that wanted to connect via OLEDB to an sql server database. However, I recently created an adp project in MS Access that seemed to connect without any problems, even though the Client Connectivity component wasn't installed. I am now confused exactly what that install option actually does. Can someone give me a clue?
It installs a plugin called "Enterprise Manager", which provides a highly
functional graphical user interface for managing all aspects of SQL Server and its databases. Regards, Graham R Seach Microsoft Access MVP Sydney, Australia [quoted text, click to view] <arch> wrote in message news:424a7e03$1@funnel.arach.net.au... >I was under the impression that the Client Connectivity install was >required > for every machine on a LAN network that wanted to connect via OLEDB to an > sql server database. However, I recently created an adp project in MS > Access that seemed to connect without any problems, even though the Client > Connectivity component wasn't installed. I am now confused exactly what > that install option actually does. Can someone give me a clue? > > >
My understanding was that MDAC included the client network libraries ...
MDAC is a prime example of DLL hell problem, it comes in many versions and is bundled with many microsoft products. As long as the client machines have MDAC2.6 (or higher) you will be able to connect to sql server.2000 The following versions of windows come bundled with MDAC WinXP Win2K Lower versions of MDAC might also work as long as you are not using a named instance of SQL Server. A quick way to find your version of MDAC is to look up the following registry entry, it is not reliable but works in most cases: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version hth -- Vikram Vamshi Eclipsys Corporation [quoted text, click to view] "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message news:sm6l41l30f6qq0idp4lb5ascf0vkb5amas@4ax.com... > Client connectivity installs MDAC and the network > libraries. Most applications only need MDAC. Generally you > will only need MDAC which is already on most PC so the > client connectivity install is usually not required. > > -Sue > > On Wed, 30 Mar 2005 18:38:32 +0800, <arch> wrote: > >>I was under the impression that the Client Connectivity install was >>required >>for every machine on a LAN network that wanted to connect via OLEDB to an >>sql server database. However, I recently created an adp project in MS >>Access that seemed to connect without any problems, even though the Client >>Connectivity component wasn't installed. I am now confused exactly what >>that install option actually does. Can someone give me a clue? >> >> >
Yes,
Tell me me about it. I have an application that I am suspecting uses DB-LIB to talk to the SQL Server and I would always have to do the install of Client Network Utility on each workstation to go along with the app. But lately I had a user that could do without it - Go figure? And then I ran into the user who was missing the Network DB Library Communications Layer when I installed Client Network Utility 2000 on his machine to talk to SQL Server 2000 Server, so I had to revert to the SQL Server Client Network Utility 7.0 to make it work. [quoted text, click to view] "Vikram Vamshi" wrote:
> My understanding was that MDAC included the client network libraries ... > > MDAC is a prime example of DLL hell problem, it comes in many versions and > is bundled with many microsoft products. > > As long as the client machines have MDAC2.6 (or higher) you will be able to > connect to sql server.2000 > The following versions of windows come bundled with MDAC > WinXP > Win2K > > Lower versions of MDAC might also work as long as you are not using a named > instance of SQL Server. > > A quick way to find your version of MDAC is to look up the following > registry entry, it is not reliable but works in most cases: > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version > > hth > -- > Vikram Vamshi > Eclipsys Corporation > "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message > news:sm6l41l30f6qq0idp4lb5ascf0vkb5amas@4ax.com... > > Client connectivity installs MDAC and the network > > libraries. Most applications only need MDAC. Generally you > > will only need MDAC which is already on most PC so the > > client connectivity install is usually not required. > > > > -Sue > > > > On Wed, 30 Mar 2005 18:38:32 +0800, <arch> wrote: > > > >>I was under the impression that the Client Connectivity install was > >>required > >>for every machine on a LAN network that wanted to connect via OLEDB to an > >>sql server database. However, I recently created an adp project in MS > >>Access that seemed to connect without any problems, even though the Client > >>Connectivity component wasn't installed. I am now confused exactly what > >>that install option actually does. Can someone give me a clue? > >> > >> > > > >
Nope that's not correct. There are additional library files
with the client connectivity components that are not installed with MDAC. The Jet drivers are also installed which are no longer part of MDAC since MDAC 2.6. Most often, people need to install the client connectivity components to get DB-Lib (ntwdblib.dll). MDAC and client connectivity install are definitely not the same thing although as I already posted, most of the time MDAC only will suffice but not always. -Sue On Thu, 31 Mar 2005 18:25:31 -0500, "Vikram Vamshi" [quoted text, click to view] <vikram.vamshi@nospam.com> wrote:
>My understanding was that MDAC included the client network libraries ... > >MDAC is a prime example of DLL hell problem, it comes in many versions and >is bundled with many microsoft products. > >As long as the client machines have MDAC2.6 (or higher) you will be able to >connect to sql server.2000 >The following versions of windows come bundled with MDAC >WinXP >Win2K > >Lower versions of MDAC might also work as long as you are not using a named >instance of SQL Server. > >A quick way to find your version of MDAC is to look up the following >registry entry, it is not reliable but works in most cases: >HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version > >hth
That is correct. MDAC does not include ntwdblib. You need to
install the client connectivity components (or use sqlredis). Other applications may distribute ntwdblib which is why one of the users may have not experienced the error. Per the Redist.txt file on the SQL Server CD, you can redistribute ntwdblib. You can find the files installed by MDAC in the MDAC manifest. I believe Vines and Apple Talk as well as the Jet drivers are the other pieces you won't get with just MDAC. http://support.microsoft.com/?kbid=828396 -Sue On Fri, 1 Apr 2005 14:33:01 -0800, "Cathy Boehm" [quoted text, click to view] <CathyBoehm@discussions.microsoft.com> wrote:
>Yes, >Tell me me about it. >I have an application that I am suspecting uses DB-LIB to talk to the SQL >Server and I would always have to do the install of Client Network Utility on >each workstation to go along with the app. But lately I had a user that could >do without it - Go figure? >And then I ran into the user who was missing the Network DB Library >Communications Layer when I installed Client Network Utility 2000 on his >machine to talk to SQL Server 2000 Server, so I had to revert to the SQL >Server Client Network Utility 7.0 to make it work. > > >"Vikram Vamshi" wrote: > >> My understanding was that MDAC included the client network libraries ... >> >> MDAC is a prime example of DLL hell problem, it comes in many versions and >> is bundled with many microsoft products. >> >> As long as the client machines have MDAC2.6 (or higher) you will be able to >> connect to sql server.2000 >> The following versions of windows come bundled with MDAC >> WinXP >> Win2K >> >> Lower versions of MDAC might also work as long as you are not using a named >> instance of SQL Server. >> >> A quick way to find your version of MDAC is to look up the following >> registry entry, it is not reliable but works in most cases: >> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version >> >> hth >> -- >> Vikram Vamshi >> Eclipsys Corporation >> "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message >> news:sm6l41l30f6qq0idp4lb5ascf0vkb5amas@4ax.com... >> > Client connectivity installs MDAC and the network >> > libraries. Most applications only need MDAC. Generally you >> > will only need MDAC which is already on most PC so the >> > client connectivity install is usually not required. >> > >> > -Sue >> > >> > On Wed, 30 Mar 2005 18:38:32 +0800, <arch> wrote: >> > >> >>I was under the impression that the Client Connectivity install was >> >>required >> >>for every machine on a LAN network that wanted to connect via OLEDB to an >> >>sql server database. However, I recently created an adp project in MS >> >>Access that seemed to connect without any problems, even though the Client >> >>Connectivity component wasn't installed. I am now confused exactly what >> >>that install option actually does. Can someone give me a clue? >> >> >> >> >> > >> >> >>
Ooops!
Forgot all about DB-Lib, it has been ages since we stopped using it ... We don't need the JET drivers to talk to SQL, do we? -- Vikram Vamshi Eclipsys Corporation [quoted text, click to view] "Sue Hoegemeier" <Sue_H@nomail.please> wrote in message news:71e0511ub4tpq20099n5lnl4amra6dt28o@4ax.com... > Nope that's not correct. There are additional library files > with the client connectivity components that are not > installed with MDAC. The Jet drivers are also installed > which are no longer part of MDAC since MDAC 2.6. Most often, > people need to install the client connectivity components to > get DB-Lib (ntwdblib.dll). > MDAC and client connectivity install are definitely not the > same thing although as I already posted, most of the time > MDAC only will suffice but not always. > > -Sue > > On Thu, 31 Mar 2005 18:25:31 -0500, "Vikram Vamshi" > <vikram.vamshi@nospam.com> wrote: > >>My understanding was that MDAC included the client network libraries ... >> >>MDAC is a prime example of DLL hell problem, it comes in many versions and >>is bundled with many microsoft products. >> >>As long as the client machines have MDAC2.6 (or higher) you will be able >>to >>connect to sql server.2000 >>The following versions of windows come bundled with MDAC >>WinXP >>Win2K >> >>Lower versions of MDAC might also work as long as you are not using a >>named >>instance of SQL Server. >> >>A quick way to find your version of MDAC is to look up the following >>registry entry, it is not reliable but works in most cases: >>HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DataAccess\Version >> >>hth >
Don't see what you're looking for? Try a search.
|
March 2003
May 2003
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |