Good answers. Naturally they give rise to some further questions... ;-) a) Is there any risk / performance hit with installing DMO on SQL 2005? b) How do I create a System DSN? Do you just need one, or one per SQL server, or one per DB?
Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 Ad eundum quo nemo ante iit "Dirk Bulinckx" <[EMAIL PROTECTED]> Sent by: Servers Alive Discussion List <[email protected]> 22/01/2008 12:45 Please respond to Servers Alive Discussion List <[email protected]> To Servers Alive Discussion List <[email protected]> cc Subject RE: [SA-list] MS SQL checks for dummies The built-in MS SQL check of Servers ALive uses SQL DMO. And need to SQL DMO libs on the client side (being on the Servers Alive system). SQL DMO is an "interface" that is by default installed on MS SQL 6.x/7.x/2000 NOT on SQL2005. There is an add-on pack for SQL2005 that includes SQL DMO for SQL2005, if you install that on SQL2005 then it *should* be possible to use the MS SQL check of Servers Alive. IF the SQL server uses integrated/NT security (and not SQL security) then the check will not be able to authenticated if Servers Alive is running as service (at least that is what our testing showed) The built-in MS SQL check will only check if the database is running and in multi-user, nothing else. If you want to check if a mySQL db is up and running, then you should use the mySQL addon that is on http://www.woodstone.nu/salive/addons.asp (http://www.woodstone.nu/salive/addons.asp) This COM check can not only check if the db is up and running, it can also check if a SQL statement can be executed. If you want to do a SQL query towards a db and check the result of that SQL query, then you should use the ODBC add-on (http://www.woodstone.nu/salive/addons.asp (http://www.woodstone.nu/salive/addons.asp)) This will then use the installed ODBC drivers in order to access the (remote) database. For this checktype to work you will need to create a SYSTEM DSN. Dirk Bulinckx. From: Servers Alive Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of [EMAIL PROTECTED] Sent: Tuesday, January 22, 2008 1:01 PM To: Servers Alive Discussion List Subject: [SA-list] MS SQL checks for dummies Folks, There are quite a few threads in the archive about checking MS SQL from within SA, and as a db dummy I'm struggling to work out which ones apply to what, how to configure etc etc. It all gets very confusing with talk of DMO, SMO and other stuff like that. I can't see anything in the documentation section about db checks, so I wonder if someone would be willing to put something together... What I want to do (and I'm sure I can't be alone) is monitor a variety of different databases, which exist on MS SQL 2000 or MS SQL 2005 servers. I need to find answers to questions like: * When should I use the ODBC COM check, and when should I use SA's built-in SQL server check? * Do I need to install any additional software on the SA box to use either of these? (i.e. some sort of SQL client utilities?) Where would I get these? * Do I need to configure DSN things on the SA box? How? * I want to test not only whether a db is alive, but also if it is growing too much, and when the last record was added. How can I do this? * Is there anything else that I *should* be checking routinely on a SQL server? Or, to put it another way, am I asking the right questions?? Also, just to complicate it further, we have a MySQL server as well. There's a separate MySQL check for SA, but that appears simply to check if the db is available to log in to. Are there ways (using the ODBC check?) of doing more than that? Answers on a postcard (or several...) Cheers, Ian _________________________________ Ian K Gray OEL IS - European Infrastructure Support Tel: +44 1236 502661 Mob: +44 7881 518854 Ad eundum quo nemo ante iit ______________________________________________________________________________ Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: Although the Company has taken reasonable precautions to ensure that no viruses are present in this e-mail, the Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list. ______________________________________________________________________________ Any opinions expressed in this email are those of the individual and not necessarily of the Company. This email and any files transmitted with it, including replies and forwarded copies (which may contain alterations) subsequently transmitted from the Company are confidential and solely for the use of the intended recipient. It may contain material protected by legal privilege. If you are not the intended recipient or the person responsible for delivering to the intended recipient, be advised that you have received this email in error and that any use is strictly prohibited. Please notify the sender immediately of the error and delete any copies of this message Warning: Although the Company has taken reasonable precautions to ensure that no viruses are present in this e-mail, the Company cannot accept responsibility for any loss or damage arising from the use of this e-mail or attachments. To unsubscribe send a message with UNSUBSCRIBE as subject to [email protected] If you use auto-responders (like out-of-the-office messages), then make sure that they are not send to the list nor to the individual members of the list that send a message. Doing this will get you removed from the list.
