MSSQL Client Software?

What do these SQL client tools provide that establish the connection?


"David Gugick" wrote in message

 > Jamie wrote:
  >> We have Windows XP workstations and I'm trying to figure out what this
  >> Client software is? Can anyone give me some information on this?
  >>
  >> Installing MSSQL Client Software
  >> Before installing the application, you will need to install your MSSQL
  >> Client software that
  >> matches the version of your MSSQL server. After installing the Client
  >> software, it is a good idea to test
  >> your connection to the MSSQL database. Be sure to remember your
  >> Server Name and
  >> Database Name for the Database, as you'll need it during the
  >> installation.
 >
 > That refers to the SQL Server Client Tools that come with SQL Server. They
 > are installed directly from the SQL Server CD.
 >
 > --
 > David Gugick
 > Imceda Software
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com</font" target="_blank">www.imceda.com</font</a>>
 >> Stay informed about: MSSQL Client Software? 

Jamie wrote:
 > What do these SQL client tools provide that establish the connection?
 >

They install some native drivers in addition to the tools themselves.
Most client applications require installation of MDAC, but nothing more,
for SQL Server access. I can only guess whatever you're installing has
some need to access the client tools. No way of knowing, however. Maybe
if you provide more information about what you're doing.

--
David Gugick
Imceda Software
<a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com" target="_blank">www.imceda.com</a>
 >> Stay informed about: MSSQL Client Software? 

That is what they say. I just don't understand why? I have never had an
application need this and it makes me wonder why they wrote theirs to need
this.

As far as MDAC isn't this automatically already on XP? I have other apps
that need MDAC and it doesn't install MDAC with XP like it used to with 98.

I know it needs this file - ntwdblib.dll and I guess the client installs
this file. Is there any reason why it would need others or do you know what
this file does?

Jamie

"David Gugick" wrote in message

 > Jamie wrote:
  >> What do these SQL client tools provide that establish the connection?
  >>
 >
 > They install some native drivers in addition to the tools themselves. Most
 > client applications require installation of MDAC, but nothing more, for
 > SQL Server access. I can only guess whatever you're installing has some
 > need to access the client tools. No way of knowing, however. Maybe if you
 > provide more information about what you're doing.
 >
 > --
 > David Gugick
 > Imceda Software
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com</font" target="_blank">www.imceda.com</font</a>>
 >> Stay informed about: MSSQL Client Software? 

Jamie wrote:
 > That is what they say. I just don't understand why? I have never
 > had an application need this and it makes me wonder why they wrote
 > theirs to need this.
 >
 > As far as MDAC isn't this automatically already on XP? I have other
 > apps that need MDAC and it doesn't install MDAC with XP like it used
 > to with 98.
 > I know it needs this file - ntwdblib.dll and I guess the client
 > installs this file. Is there any reason why it would need others or
 > do you know what this file does?
 >
 > Jamie

ntwdblib.dll is the client library for dbLib. I think it's a SQL 7 DLL
and not a SQL 200 one. not sure. Why not contact the software
manufacturer and see why the client tools are required. Maybe the
application uses tools like OSQL or BCP.

--
David Gugick
Imceda Software
<a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com" target="_blank">www.imceda.com</a>
 >> Stay informed about: MSSQL Client Software? 

AFAIK, dblib has not been updated in SQL Server 2000 from the previous
version. Microsoft has made it clear years back that dblib is a dead-end so
if folks continue to develop on dblib, they're asking for trouble.

As for the "client software", that's probably just a generic set of
instructions from the ISVs especially if they support other databases like
Oracle (which has a big client component and we're not even talking tools
here). Apart from that, David's guess on apps is about as close as it gets.


joe.


"David Gugick" wrote in message

 > Jamie wrote:
  >> That is what they say. I just don't understand why? I have never
  >> had an application need this and it makes me wonder why they wrote
  >> theirs to need this.
  >>
  >> As far as MDAC isn't this automatically already on XP? I have other
  >> apps that need MDAC and it doesn't install MDAC with XP like it used
  >> to with 98.
  >> I know it needs this file - ntwdblib.dll and I guess the client
  >> installs this file. Is there any reason why it would need others or
  >> do you know what this file does?
  >>
  >> Jamie
 >
 > ntwdblib.dll is the client library for dbLib. I think it's a SQL 7 DLL and
 > not a SQL 200 one. not sure. Why not contact the software manufacturer and
 > see why the client tools are required. Maybe the application uses tools
 > like OSQL or BCP.
 >
 > --
 > David Gugick
 > Imceda Software
<font color=purple> > <a rel="nofollow" style='text-decoration: none;' href="http://www.imceda.com</font" target="_blank">www.imceda.com</font</a>>
 >> Stay informed about: MSSQL Client Software?