This is the code that I have (using DBD::ODBC) which works just fine:

sub connectdb {
    my ($data_source, $database, $user_id, $passwd ) = 
        qw( server_hostname_or_IP database_instance username password 
+);
    my $conn_string = "driver={SQL Server};Server=$data_source;Databas
+e=$database;UID=$user_id;PWD=$passwd";
    my $dbh = DBI->connect( "DBI:ODBC:$conn_string" ) or die $DBI::err
+str;
    return $dbh;
}
[download]

Cheers,
Darren :)

PS. It's when you try connecting to a MS-SQL server from a Linux box that the fun really begins! But in that case, I found this tutorial to be an absolute godsend :)

To access SQL Server from Perl on windows, you have two clear choices and some unclear ones. Using DBD::Sybase is one of the unclear ones.

Your two simple choices are DBD::ODBC and DBD::ADO. Both of those work very well with SQL Server if you're on a Windows variant. Generally people fall back on using the Sybase driver (with freetds) when they have to connect to SQL Server from a Linux, Unix, or other non-Windows machine.

A couple of notes in general: Installing some Perl modules requires a compiler; DBD::Sybase is one of them. A very good workaround to having a compiler, if you're using ActiveState Perl, is to use ppm, the Perl Package Manager that comes with the ActiveState installation. You may have to dig around for a particular PPM package; Google is your friend here.

Even for packages that don't require compilation, it's often better to use an installer like ppm or the CPAN.pm module. That way you'll be sure everything is where it needs to be, that prerequisites are available, and so on.

Second general note: you don't need to explicitly call out the DBD package you want (in general). You can just do:

use DBI;
[download]

HTH

Try 'dbi:' in uppercase:

my $dbh = DBI->connect('DBI:Sybase:', 'sa', '');
[download]

This will have no effect whatsoever. The pattern match against the DSN is done case-insensitively. Here is the appropriate line from DBI.pm (version 1.50):

    # extract dbi:driver prefix from $dsn into $1
    $dsn =~ s/^dbi:(\w*?)(?:\((.*?)\))?://i
            or '' =~ /()/; # ensure $1 etc are empty if match fails
[download]

Do not rebuke them with harsh words ... but rather lead them gently - with URLs - so that they may learn wisdom.

oops, that's true...

Then DBD::Sybase doesn't seem to be installed correctly. If there's a Sybase*.ppd in the zip file, try to execute the following command in the directory with the ppd-file (let's assume its name is Sybase-1.2.3.ppd)

ppm install Sybase-1.2.3.ppd

http://theoryx5.uwinnipeg.ca/ppms/ might also be interesting for you

Best regards,
perl -e "s>>*F>e=>y)\*martinF)stronat)=>print,print v8.8.8.32.11.32"

You probably need install this module "better"; unpacking could be not enough. Which directory you unpacked into?
Also, it could perfectly be your perl DLLs do not have executable permissions, or so.
(your file system is NTFS?)

Make stripped following excerpt from your code to pass compiling:

use DBI;
use DBD::ODBC;
use DBD::Sybase;
[download]

$ENV{SYBASE} = 'C:\Program Files\Microsoft SQL Server\80\Tools\BINN';
[download]

and I advice you to get rid of your following hack: $ENV{SYBASE} = 'C:\Program Files\Microsoft SQL Server\80\Tools\BINN';

If you're using DBD::Sybase, you need this line either in a BEGIN block or set in your environment before invoking the script.

The sybase client libs use the environment variable SYBASE to locate the interfaces (or sql.ini for w32) file. The interfaces file is where the logical name of the database (used in the connection method) is mapped to the actual machine/port.

-derby

all true, but such hard-coding of paths isn't good.

You will have problems running this script elsewhere.

Much better to find another way of supplying that ENV variable: helper .BAT, or real environment change, or finding installation path via registry, or whatever.

If accessing MS SQL Server 2000/2005 from Linux/Unix, then use FreeTDS to build the DBD::Sybase against. The reason for this, is that if the SQL Server is using integrated authentication, then Sybase's OpenClient is unable to connect. FreeTDS is able to work with integrated authentication.

Thanks to each one of you.. Will verify and get back.. Regards