Re: MS SQL Server

You didn't say if your client perl program was going to be running on NT or UNIX. If it is going to be running on NT, you should have no problems, DBD::ODBC works just fine and is as good performance-wise because MS Sql is as-fast w/ ODBC as with any other driver:

use DBI;
my $dbh = DBI->connect("dbi:ODBC:MQIS","USER","PASSWORD");
[download]

where MQIS is your ODBC DSN.

If your client is gonna run on UNIX (or any OS for which MS does not provide client-side ODBC libraries) you have 2 choices:

DBD::Proxy - run a proxy DBD on an NT box and have your perl programs use DBD::Proxy to connect to the proxy.
3rd party ODBC driver - there are some 3rd party ODBC drivers for MS Sql server (some commercial, some not) that you could use. I've never used these (don't even know where to get them), but I have heard that they exist :)

Comment on Re: MS SQL Server Download Code

Replies are listed 'Best First'.
RE: Re: MS SQL Server by TStanley (Canon) on Aug 29, 2000 at 18:24 UTC
Openlink Software is a company that has a very good generic type of ODBC driver, that will connect to just about any type of database, whether it is Oracle, MySQL, Informix, MS SQL Server, Solid, etc. TStanley There can be only one!	[reply]
RE: RE: Re: MS SQL Server by TStanley (Canon) on Oct 22, 2000 at 06:56 UTC
An update to this post..The Openlink drivers work with pretty much any database at the moment, except MS SQL Server. It seems their code has a bug in it, of which they are aware, and it will be fixed in their next release, which is due out within (HOPEFULLY) the next month. The drivers for Oracle work quite well, and the only problem that has been noted, is that you need to use a SQLDRIVERCONNECT to connect to the database, instead of SQLCONNECT. This has been reported to Openlink, and will be addressed in the next release. TStanley UPDATE (13 NOV 00): The new drivers are out and unfortunately, the same bug is still there.	[reply]