So far, I really like what I'm seeing in SQLResponse. It is great to have so much information readily available. The configuration options, breadth of alerts and recommendations as well as the detail provided should make life easier - when I learn how to use the product.
I have encountered a problem with the Alert Service. Soon after installing, it stopped being able to connect to SQL Servers. It could not connect to any, even those that it had connected to previously that had been removed and then added again. Restarting the service fixed the problem.
However, restarting the service wasn't easy. I attempted to restart it from Computer Management: Services. The service would not stop. I had to terminate it from Task Manager. The service then started and was able to connect to my SQL Servers.
When I left the office last Thursday, the service was running and sending alerts. Sometime between then and this morning, it stopped sending alerts. I again attempted to restart the service. It would not stop. I terminated it in Task Manager, restarted the service and all is well.
I am running the service on a Windows Server 2003 64-bit OS. The server has 32GB of RAM and two quad processors. I'm currently running 11 SQL Server 2005 64-bit instances (test) on this server. The SQLResponse Alert service is configured to monitor these instances.
I installed SQLResponse on this server because it is a test server. Do you think it would be better to install it elsewhere, perhaps on a server without any SQL Server instances? Has anyone encountered problems running the service on a 64-bit OS?
Thanks for all you help and great products.
Sorry you've had problems - I believe there was an issue with the RC in that if it failed to contact a SQL Server for some reason then when the server came back up it didn't correctly restart the monitoring. This is fixed for the final release.
I have encountered a problem with the Alert Service. Soon after installing, it stopped being able to connect to SQL Servers. It could not connect to any, even those that it had connected to previously that had been removed and then added again. Restarting the service fixed the problem.
However, restarting the service wasn't easy. I attempted to restart it from Computer Management: Services. The service would not stop. I had to terminate it from Task Manager. The service then started and was able to connect to my SQL Servers.
When I left the office last Thursday, the service was running and sending alerts. Sometime between then and this morning, it stopped sending alerts. I again attempted to restart the service. It would not stop. I terminated it in Task Manager, restarted the service and all is well.
I am running the service on a Windows Server 2003 64-bit OS. The server has 32GB of RAM and two quad processors. I'm currently running 11 SQL Server 2005 64-bit instances (test) on this server. The SQLResponse Alert service is configured to monitor these instances.
I installed SQLResponse on this server because it is a test server. Do you think it would be better to install it elsewhere, perhaps on a server without any SQL Server instances? Has anyone encountered problems running the service on a 64-bit OS?
Thanks for all you help and great products.