Re: sql server database connectivity error

Selvakumar:

Of the listed drivers in the end of your question, I'd use ODBC. I use it to access both MS SQL and Oracle databases with no issues.

...roboticus

Comment on Re: sql server database connectivity error

Replies are listed 'Best First'.
Re^2: sql server database connectivity error by afoken (Chancellor) on Sep 23, 2009 at 04:35 UTC
ODBC adds a lot of overhead, and does not offer all of the features you could use with a native driver. I would always try to connect to the database using a native driver (there are lots of native DBDs on CPAN), then fall back to the fat and slow ODBC. For MS SQL, you are right, ODBC is the way with the least pain, since there is no real native driver. You could also use ADO, which adds even more overhead, or you could try DBD::Sybase plus FreeTDS: MS SQL Server is a fork of Sybase 4.2, and they still share their communication protocol. Alexander -- Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)	[reply]

Replies are listed 'Best First'.

Re^2: sql server database connectivity error
by afoken (Chancellor) on Sep 23, 2009 at 04:35 UTC

ODBC adds a lot of overhead, and does not offer all of the features you could use with a native driver. I would always try to connect to the database using a native driver (there are lots of native DBDs on CPAN), then fall back to the fat and slow ODBC. For MS SQL, you are right, ODBC is the way with the least pain, since there is no real native driver. You could also use ADO, which adds even more overhead, or you could try DBD::Sybase plus FreeTDS: MS SQL Server is a fork of Sybase 4.2, and they still share their communication protocol.

Alexander

--
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)

[reply]