Comments on: How Events Monitoring can Prevent IT Disasters (Part 2) http://www.gfi.com/blog/events-monitoring-prevent-disasters-part-2/?utm_source=rss&utm_medium=rss&utm_campaign=events-monitoring-prevent-disasters-part-2 Brought to you by GFI Software Fri, 09 Aug 2013 12:13:46 +0000 hourly 1 By: Ryan_5187 http://www.gfi.com/blog/events-monitoring-prevent-disasters-part-2/comment-page-1/#comment-24605 Ryan_5187 Thu, 10 Mar 2011 03:01:35 +0000 http://www.gfi.com/blog/?p=3169#comment-24605 Events Monitoring should also be paired with Performance Testing. The two are dependent on each other.

Performance Testing encompasses and evaluates a system’s overall functions. It can establish the effectiveness and pace of computers and other IT systems (such as websites, network, software / programs, etc).

Performance Testing can be done in two methods: quantitative and qualitative.

]]> By: Mohammed S Ali http://www.gfi.com/blog/events-monitoring-prevent-disasters-part-2/comment-page-1/#comment-24451 Mohammed S Ali Wed, 09 Mar 2011 12:12:47 +0000 http://www.gfi.com/blog/?p=3169#comment-24451 Hi Gordon,

Thanks for your comment.

The size of a database matters because a large database may have an impact on the performance and the time required to process a SQL statement.

Timeout happens more often, if the DBMS is not able to return a result within the timeout value of the appliance
which is querying the database. Therefore it is wise to keep the size of a database always low.

]]> By: Gordon Howard http://www.gfi.com/blog/events-monitoring-prevent-disasters-part-2/comment-page-1/#comment-24344 Gordon Howard Tue, 08 Mar 2011 20:49:21 +0000 http://www.gfi.com/blog/?p=3169#comment-24344 Wouldn’t you just want the most storage possible to have the largest log of events? Obviously performance is a key factor but just take the system with the best performance and torque up the database size and shouldn’t you have the best possible system right there?

]]>