Idera Uptime Download _VERIFIED_
Roshelle Ravenel
Users upgrading from Uptime Infrastructure Monitor 7.8.0 to 7.8.2 or later who use MSSQL as a database backend should check their [uptime install folder]\uptime.conf and take note of the drivers used. If the sqljdbc4.jar driver is not being used, nothing needs to be done. Look for:
If dbDriverClass is uncommented, you should comment it out prior to running the upgrade. If you wish to continue using the MSSQL native JDBC driver, you should copy sqljdbc4.jar out of the [uptime install folder]\core folder prior to upgrading as it will get removed during the upgrade. If this task is not performed, you will notice that the upgrade program fails to reinstall the MSSQL JDBC driver and the upgrade will break.
You must download the sqljdbc4.jar driver for MSSQL ( -us/download/details.aspx?id=11774 and put it in the uptime/core directory after the upgrade, uncomment the line we commented prior, and restart Uptime data collector (core in Linux) service to pick up the change.
Uptime Infrastructure Monitor 7.9 introduced the use of encrypted passwords in the uptime.conf and uptime-controller.conf files. In order to change the default Uptime username and password, you must first change them in the datastore (i.e. MySQL, MSSQL, or Oracle). Then use the UptimeConfigUtility tool to apply the changes to the uptime.conf and uptime-controller.conf files.
If the database and monitoring station exist on the same machine, then drivers are already installed. Only DSN will need to be created. Also, the exact name as specified in these steps must be used for the connection or the gadgets will not work. If you wish to use a different connection name, you must edit the uptimeDB.php file accordingly.
Linux based monitoring stations will require the unixODBC package to be installed. This package should include the /usr/lib64/libtdsodbc.so.0 SQL Server ODBC Driver needed for MSSQL/SQLserver. Which is also the example provided in uptimeDB.php
The OpSmart offshore team of certified experts have done extentensive customer suport & troubleshotting of the Uptime platform and have been supported several implemetation. we have also developed intergerations end engancements for uptime & its customers.
I know that Uptime Robot has a new plan, which is the PRO ( -uptime-robot-pro-for-1-minute-checks-andor-more-monitors/) and well I was just wondering if there are any other website or server monitoring services that are cheaper than Uptime Robot?
Idera, a provider of application management solutions for Windows and Linux, has introduced SharePoint diagnostic manager 2.7, which provides new capacity planning features enabling administrators to predict when they will need to expand or upgrade hardware in order to prevent performance issues caused by growth of SharePoint sites and content. This release also provides expanded analytics for SQL Server performance, web page health and uptime, and content usage and composition.
An enhanced security model also enables SharePoint diagnostic manager users to restrict access to data stored in its central repository, thus preventing unauthorized access to sensitive configuration data such as stored server names, and database names. In addition, SharePoint diagnostic manager fully supports SharePoint farms running on Microsoft SQL Server 2012.
The new analytics and capacity planning features are "a must-have" for a mission-critical and storage-dependent application like SharePoint, according to Wayne Washburn, director of SharePoint Products at Idera. "SharePoint diagnostic manager gathers and stores massive amounts of data to analyze and turn into actionable information and alerts."
Tim Rottach, director of product marketing at Couchbase, emphasized that between customers and the current market, application needs have changed. They are expected to be personalized and responsive, available everywhere, real-time, dependable, developed efficiently, and deployed effectively with 100% uptime at global scale.