Comments
Sort by recent activity
Hi MHolahan,
To stop SQL Response monitoring all servers you can stop the Alert Repository Service, there can be more than one Alert Repository Service however you would have set up any additional ones.
If you want to stop monitoring just one server you can remove it from the GUI, when removing you can opt to keep the Alert Repository files and not deactivate so if you add the server again later, it is in the same state as when you deleted it.
You should only deactivate if you will no longer want to monitor that server and would like to monitor a different server.
I hope this helps. / comments
Hi MHolahan,
To stop SQL Response monitoring all servers you can stop the Alert Repository Service, there can be more than one Alert Repository Service however you would have set up any additional ...
Hi Stephen,
I apologise you are encountering this error.
What version of SQL Server are you running and what version of SQL Backup do you have?
Does this also happen when running backups?
The log files should be kept here on 2008 Server :
$:\ProgramData\Red Gate\SQL Backup\log\<instance name>
Alternatively you can open the SQL Backup GUI and choose Tools>Options to find the location.
If you could send some log files to support@red-gate.com quoting reference F0020565 that would be great. / comments
Hi Stephen,
I apologise you are encountering this error.
What version of SQL Server are you running and what version of SQL Backup do you have?
Does this also happen when running backups?
The log f...
Hi mulmad,
Thank you for your suggestion, this will be considered for a future release with reference to both SQL Compare and SQL Data Compare.
Thanks. / comments
Hi mulmad,
Thank you for your suggestion, this will be considered for a future release with reference to both SQL Compare and SQL Data Compare.
Thanks.
Hi CrispinH,
Thank you for the suggestion, this has been requested before and will be considered for a future release. / comments
Hi CrispinH,
Thank you for the suggestion, this has been requested before and will be considered for a future release.
This was resolved via support call and the resolution was to enable Auto list members and Parameter information under Tools>Options>Text Editor>Transact-SQL>General / comments
This was resolved via support call and the resolution was to enable Auto list members and Parameter information under Tools>Options>Text Editor>Transact-SQL>General
Hi Alex,
Thank you for the feedback, this will be considered for a future release.
Thanks again. / comments
Hi Alex,
Thank you for the feedback, this will be considered for a future release.
Thanks again.
Hi Karllu,
This feature isn't currently available in SQL Response however we value all feedback and it will be considered for a future release.
Thanks, / comments
Hi Karllu,
This feature isn't currently available in SQL Response however we value all feedback and it will be considered for a future release.
Thanks,
Hi Dan,
SQL Data Compare will set the Primary key or an Index as the comparison key when it finds them.
You can select customer comparison keys or select a specific index by using the Tables and Views tab.
You could try also try setting a Where clause from the same tab to eliminate older data rows which you know will never change.
A further option would be to un check the Show identical values in results from the Options tab under Comparison Behaviour and select Use Checksum Comparison.
I hope this helps, / comments
Hi Dan,
SQL Data Compare will set the Primary key or an Index as the comparison key when it finds them.
You can select customer comparison keys or select a specific index by using the Tables and Vi...
Hi Mike,
The baseline is the average of the previous 10 job runs, unfortunately with a max of 99% this will still alert you for jobs which take over 20 seconds.
There is a current feature request to set a value higher than 99% which I have updated with your input.
Thank you for bringing this up. / comments
Hi Mike,
The baseline is the average of the previous 10 job runs, unfortunately with a max of 99% this will still alert you for jobs which take over 20 seconds.
There is a current feature request t...
Hi Tom,
Unfortunately there is no way to force the copy of the log file in the result of an error. Any error code over 500 represents an error and thus post backup tasks are not executed.
Do you have a lot of backup jobs which all run around the same time?
If you have a separate job for each database and they are scheduled to start at the same time this error will be more likely to occur.
Thank you for your feedback regarding an option to force the copy in the event of this error. / comments
Hi Tom,
Unfortunately there is no way to force the copy of the log file in the result of an error. Any error code over 500 represents an error and thus post backup tasks are not executed.
Do you h...