Hello!
The SQL Response Release Candidate is now ready for you to try out. You can download it from
ftp://ftp.red-gate.com/releasecandidate ... 0.1596.exe
If you tested the SQL Response beta v1 earlier this year, you will first need to uninstall the beta before installing the Release Candidate. This can be done as follows:
- Uninstall the "SQL Response Incident Repository" and "SQL Response 1" applications via Add/Remove Programs.
- Remove any remaining files from "C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Response\".
Information about requirements for the Release Candidate can be viewed here:
http://www.red-gate.com/products/SQL_Re ... ements.htm
SQL Response Release Candidate will expire on 14th October, 2008. Please also see the list below of known issues.
As mentioned in our welcome message, we would love to hear what you think about the SQL Response Release Candidate. We encourage you to post your feedback on this forum, and we promise we’ll respond to your comments. We plan to launch the first, full version of SQL Response towards the beginning of October, so any feedback that you can offer as soon as possible on the Release Candidate would be greatly appreciated; this gives us the best chance possible to take on board your comments and make any adjustments and tweaks to SQL Response before code lockdown. There will also be three luxury Red Gate goodie boxes for the first three people to email detailed feedback to us on how SQL Response has performed under different, extreme and varying conditions.
Many thanks again for your participation, and the SQL Response team is looking forward to hear from you.
Known Issues:
1. Email for the alert ‘CPU utilization unusual’ is triggered every time when this alert is raised.
2. The ‘Transaction log file has excessive free space’ recommendation shows wrong count for the ‘Log files with excessive free space’ (the other values are correct).
3. The ‘Data file has excessive free space’ recommendation shows wrong count for the ‘Data files with excessive free space’ (the other values are correct).
4. The ‘Fragmented Index’ recommendation may not be generated correctly for SQL Server 2008.
5. Clearing multiple alerts may occasionally clear the first alert only.
6. The ‘SQL Server unreachable’ alert is sometimes generated instead of the ‘SQL Server login failure’ alert if the login fails for SQL Server authentication.
Thanks,
Priya
The SQL Response Release Candidate is now ready for you to try out. You can download it from
ftp://ftp.red-gate.com/releasecandidate ... 0.1596.exe
If you tested the SQL Response beta v1 earlier this year, you will first need to uninstall the beta before installing the Release Candidate. This can be done as follows:
- Uninstall the "SQL Response Incident Repository" and "SQL Response 1" applications via Add/Remove Programs.
- Remove any remaining files from "C:\Documents and Settings\All Users\Application Data\Red Gate\SQL Response\".
Information about requirements for the Release Candidate can be viewed here:
http://www.red-gate.com/products/SQL_Re ... ements.htm
SQL Response Release Candidate will expire on 14th October, 2008. Please also see the list below of known issues.
As mentioned in our welcome message, we would love to hear what you think about the SQL Response Release Candidate. We encourage you to post your feedback on this forum, and we promise we’ll respond to your comments. We plan to launch the first, full version of SQL Response towards the beginning of October, so any feedback that you can offer as soon as possible on the Release Candidate would be greatly appreciated; this gives us the best chance possible to take on board your comments and make any adjustments and tweaks to SQL Response before code lockdown. There will also be three luxury Red Gate goodie boxes for the first three people to email detailed feedback to us on how SQL Response has performed under different, extreme and varying conditions.
Many thanks again for your participation, and the SQL Response team is looking forward to hear from you.
Known Issues:
1. Email for the alert ‘CPU utilization unusual’ is triggered every time when this alert is raised.
2. The ‘Transaction log file has excessive free space’ recommendation shows wrong count for the ‘Log files with excessive free space’ (the other values are correct).
3. The ‘Data file has excessive free space’ recommendation shows wrong count for the ‘Data files with excessive free space’ (the other values are correct).
4. The ‘Fragmented Index’ recommendation may not be generated correctly for SQL Server 2008.
5. Clearing multiple alerts may occasionally clear the first alert only.
6. The ‘SQL Server unreachable’ alert is sometimes generated instead of the ‘SQL Server login failure’ alert if the login fails for SQL Server authentication.
Thanks,
Priya