I'll just throw this out there in case you're not aware...
(I will soon be dipping into this for a client port from Sybase to SQLServer; it's non-Mon related and wasn't my decision to switch from Sybase). www.freetds.org "FreeTDS is a set of libraries for Unix and Linux that allows your programs to natively talk to Microsoft SQL Server and Sybase databases." >From http://www.freetds.org/faq.html [Which Perl Library should I use] There are four options for using TDS and Perl to connect to a Sybase or MSSQL database, DBD::Sybase, DBD::ODBC, DBD::FreeTDS, and Sybperl. >From Mark Schaal: DBD::Sybase is the recommended option, and yes it does work with MSSQL. You will need to install the perl DBI module and the FreeTDS package, particularly the CTLib portion. Set your SYBASE environment variable to /usr/local/freetds and install DBD::Sybase. Don't worry too much if some of the tests fail. Do worry if the module doesn't compile. Make sure you have the most recent version of FreeTDS installed. [...] I'd be interested to know what solution you wind up with because I may also add a Mon watch for SQLServer if one gets written. ;-) Jerry Scott Prater <[EMAIL PROTECTED]> writes: > I only wish it were so easy. Unfortunately, there is no perl > DBI for SQLServer; from what I've seen on the web, most > people hack together solutions with DBI::Proxy and DBD::ODBC, > but it is by no means a trivial process. Given my prior > experience with the joys of ODBC, I'd like to avoid going > down that particular road. > I've also seen that some people have had success DBD::Sybase, > but that solution is also fraught with perils and > complications, and does not uniformly work for all versions > of SQL Server. > Being a happy Perl hacker, I'd like to write a perl script to > do the monitoring. Failing that, I could also use JDBC, and > write my monitor script in Java. Uggh, but a possible > solution. > Andrew's proposed solution of using the Concord SNMP agent on > Windows boxes to send a trap sounds intriguing. Does anyone > have comments on other preferred SNMP agents for Windows2000? > We've had many, many battles and problems with the > Microsoft-supplied agent, and have ended up junking it. I've > played a little with Net-SNMP on Windows, but it really > didn't do all that I had hoped.
