SQL Server monitoring tools(s)

[foxbox]

At the moment i have 3 SQL servers in HQ: MS Business Solutions Axapta, Business Objects and Intranet + supporting web-apps.
Later this year we will migrate our DOS (!) logistic system to something running on MS SQL. So we will install a SQL server on every plant/location (15).
There is no ICT staff in plants; we support as much as possible via the WAN from HQ.
I'm looking for the best tool(s) to monitor this. I'm espescially interested in tools that can tell me *what* is going wrong (1000 users is a very good warning system for telling me that a server is down; i don't look for tools that tell me that).

 

[JtheRipper]

Have you had a look at Quest software for SQL Server, I am not using it myself but heard that it is can monitor SQL server databases.
J.

 

[pabloj]

Quest tools are generally good, but I would ask myself a question:
"Is it a good idea to install 15 sql servers in different locations with no IT staff there and manage them centrally?"
I would consider having a central (clustered?) database that serves the plants, it's way much more manageable.

Stick to your guns

 

[Corran007]

Its more than just that, its aslo a matter of performance. i am the dba for a grocery chain. we are in the process of putting servers in ever store for an applicaiton that runs in that store. Several reason. One is performance, unless you have a very fast wan, its faster to have them locally. Second is connection. Connections go down. With locally, they are still able to operate. It really is not that big of an issue. i have written several tools to fsciliate updating and changing them to make life easier. Honestly it would be performance hell if we tried to host them centerally. plus if we lose connection, they would go down.(it happens from time to time even with tripple redundancy, since the backups dont kick in immideatly)

 

[timscronin]

You might also look at SQL Probe, used both that and Quest product, both will give you a trial demo version. Would strongly consider you get yourself a MOM (Ms Operating Managment) PC and use it to monitor the services on all you boxes.

 

[foxbox]

Thanx for your input.
The reasons for decentral SQL servers are the ones Corran007 suggested:
1. we use barcode-/chip scanning in the plants, which only work with fast response times;
2. In my part of this world bandwidth is expensive;
3. A server outtage on the central location must not lead to a production stop in 1 or more plants;