in reply to DBD::ODBC and possibly OT.

I imagine it's the remote DB server that's giving you the message. Either it has a low limit (set by your user license?), or you have a lot of scripts that are tying up connections. I know this doesn't quite answer your question, but in the absense of log information, look to the information you do have.

Additionally, I'd consult with your database vendor (Oracle? MS SQL server?) about client packages they offer that might have the monitoring features you're interested in. You don't tell us what type of environment you're running under so it's impossible to even guess at a Perl recommendation. You may be able to do this by parsing DBI trace data for all of your scripts, but this is going to be pretty complex and difficult to do in real-time.

Replies are listed 'Best First'.
RE: Re: DBD::ODBC and possibly OT.
by PsychoSpunk (Hermit) on Nov 09, 2000 at 04:48 UTC
    Thanks, Fastolfe. The reason why I failed to mention the systems that the web servers are running on is that I don't think it matters. I've got Perl running on it, so apparently I can do something Perlish.

    I'll look into seeing if their is a MS SQL supplied real-time logger. I was hoping to find something less proprietary than that, though. ++ for being first and jolting my mind. :)

    ALL HAIL BRAK!!!