Re: ODBC drivers for MSSQL
From: Craig A. Berry (craigberry_at_mac.com.spamfooler)
Date: 02/26/04
- Next message: repatch: "Re: USA will self-exterminate within 100 years!"
- Previous message: John Brandon: "ADD/DEL node from queue manager role"
- In reply to: Joseph Lamb: "ODBC drivers for MSSQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 26 Feb 2004 14:51:43 GMT
In article <912b238d.0402252128.f88bc82@posting.google.com>,
joseph_lamb@yahoo.com (Joseph Lamb) wrote:
> Is there a way to have a VMS box run a PERL script that queries a
> WIN2k MSSQL server?
There are at least two ways, and you may or may not need an ODBC driver
as your title implies. For Perl, you need to build and install the
extensions DBI and either DBD::Sybase or DBD::ODBC. These can be found
at <http://search.cpan.org>.
But before you do that, you need some primary building blocks. If you
want to go the ODBC route, you need both a driver manager and a
database-specific driver. As far as free driver managers, I recommend
unixODBC, which you can find at <http://www.unixodbc.org>. Despite the
name, it does work on VMS, though I think its current build script
needs some tweaking.
Then you need a driver that knows the tabular datastream protocol that
both Sybase and MS SQL Server speak dialects of. The only free one I'm
aware of is FreeTDS (see <http://www.freetds.org>) which I recently
ported to VMS. You can either build FreeTDS with ODBC support by
letting it know that unixODBC is its driver manager at build time, or
you can skip ODBC entirely and use DBD::Sybase directly. (Despite the
name, DBD::Sybase works with and is commonly used with MS SQL.) Your
Perl code will look about the same either way except for the connect
statement.
The foregoing recommendations assume you have a C compiler and some
familiarity with troubleshooting open source builds. If not, you'll
probably want to pursue one or more commercial packages. Even if you
do choose a commercial solution, you'd probably still have to build DBI
and DBD::ODBC yourself if you want to use Perl.
The commercial ODBC driver managers (such as the one from Attunity
someone mentioned [but also check out OpenLink and EasySoft]) often do
not connect directly to the database on the server. Instead they
communicate with an intermediate driver service on the server, which in
turn communicates with the database. This potentially introduces a
performance hit, not to mention the license cost and maintenance cost
involved in providing the service on each server that needs it. There
are advantages to these products, though, and you'd do well to talk to
their sales staffs and see what they can do for you.
- Next message: repatch: "Re: USA will self-exterminate within 100 years!"
- Previous message: John Brandon: "ADD/DEL node from queue manager role"
- In reply to: Joseph Lamb: "ODBC drivers for MSSQL"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
