Re^3: Using DBD::ODBC and cygwin to connect to MS SQL?

Well, to find out wether the stumbling block is Perl, ODBC, some driver or even the database configuration, I'd try to connect to the database via the most simple tool. "Simple" in this case means: pre-existing and easily configured.

If you're on Windows, you might have MS Access or Excel, both of which can connect to "external" sources, hidden under something like "Import external data".

There probably is the possibility to use native MSSQL. I'd try this first to see if the database is reachable at all.
I know cygwin Perl only from hearsay, but chances are that instead of DBD::ODBC you could also use DBD::ADO (I use this with Strawberry Perl), which AFAIK uses the same "native" drivers as Excel/Access.

Then I'd try ODBC (probably under "other", where you will have to select in a next step some "data source". If it is not already set up for you, you'll need it for Perl, too, anyway.

After you got that working, you can extract the connection string from the connection's properties within Excel/Access

updated "set up" url

Comment on Re^3: Using DBD::ODBC and cygwin to connect to MS SQL?

Replies are listed 'Best First'.
Re^4: Using DBD::ODBC and cygwin to connect to MS SQL? by genio (Beadle) on Jul 13, 2016 at 21:45 UTC
Hi! You can easily use an existing ODBC connection on windows by just installing DBD::ODBC. https://gist.github.com/genio/7c7fc52fcb8be5d486aa#file-03_example_perl-pl shows the DSNs for both linux/unix and Windows. Once you have an ODBC connection setup in Windows (pay attention to 32 vs 64-bit), you can use that connection easily with the DSN string on that gist.	[reply]
Re^5: Using DBD::ODBC and cygwin to connect to MS SQL? by soonix (Chancellor) on Jul 14, 2016 at 10:22 UTC
Hi! You can easily use an existing ODBC connection on windows by just installing DBD::ODBC. From the OP I can't see whether he has an existing, functioning ODBC connection or not. To rule that out, I'd try to connect to the database from a "standard" tool (first via "native" Driver, then via ODBC). BTW in your gist, this should go into the missing `01_setup_Windows.md` :-) Your cue about 32- vs. 64- bit is very important. From my last adventure in this area ISTR that Google (or even perlmonk's Super Search) had all necessary info about this point, but of course I didn't write it down :-/	[reply] [d/l]