Activity overview
Latest activity by Panagis
Version 11.2.13 - September 16, 2021
Direct download link
Features
New alert on SQL Server log entry added which can be raised by matching a regex pattern.
Improvements
The folder used to store the index files for the top query search feature is now configurable.
Added an option to set Server waits data retention settings separately on the Data settings page.
Fixes
Standard users can access the about page and retry connections on monitored servers page.
The job failing alert now only ends when the job successfully runs. Before, an alert was raised each time the job failed.
Alerts are loaded correctly after clearing them on the Alerts page.
/ comments
Version 11.2.13 - September 16, 2021
Direct download link
Features
New alert on SQL Server log entry added which can be raised by matching a regex pattern.
Improvements
The folder used to store...
Version 11.1.8 - May 13, 2021
Direct download link Features
Improved performance when the website accesses a clustered base monitor service running in multiple subnets (see https://documentation.red-gate.com/display/SM11/Installing+SQL+Monitor+with+High+Availability).
Improvements
Disable webhook notifications in alert configuration.
Fixes
Fixes overly large memory grants in SQL Process sampler.
Fixes admin access not being correctly applied when using basic authentication.
Fixed an error monitoring Azure SQL Managed instances in the business critical or premium tier.
/ comments
Version 11.1.8 - May 13, 2021
Direct download linkFeatures
Improved performance when the website accesses a clustered base monitor service running in multiple subnets (see https://documentation.re...
Hello @S_Mackedie, I can think of some possible causes of that issue. Could you please contact the support team and send them the logs? It will help us to find a solution for you. Kind regards, Panagis / comments
Hello @S_Mackedie,I can think of some possible causes of that issue.Could you please contact the support team and send them the logs?It will help us to find a solution for you.Kind regards,Panagis
Hello @rob_wingate, Thank you for letting us know. We will take it into account. Kind regards, Panagis / comments
Hello @rob_wingate,Thank you for letting us know. We will take it into account.Kind regards,Panagis
Hello @rob_wingate, Indeed, at the moment we are not exposing that via our APIs. We are happy to look into it. Can you inform us in what scenarios this will be helpful? Kind regards, Panagis / comments
Hello @rob_wingate,Indeed, at the moment we are not exposing that via our APIs.We are happy to look into it. Can you inform us in what scenarios this will be helpful?Kind regards,Panagis
Hello krisvdvijver, From the issue that you described we can't infer what's the actual problem. Could you please contact the support team? They will investigate the logs and find a solution for you. Kind regards, Panagis / comments
Hello krisvdvijver,From the issue that you described we can't infer what's the actual problem.Could you please contact the support team?They will investigate the logs and find a solution for you.Ki...
Hello @don_don, SQL Clone creates a temporary low privilege user account to run the template script. The only role of this account is the db_owner. The first issue arises because this account hasn't permissions to alter the authorization of the database, and the second because at the last step it tries to delete the temporary user, but it can't since the database is read-only. What I'd suggest is to create a PowerShell script that will call the Clone cmdlet and after that it will alter the authorization of the database and make it read-only. Kind regards, Panagis / comments
Hello @don_don,SQL Clone creates a temporary low privilege user account to run the template script. The only role of this account is the db_owner.The first issue arises because this account hasn't ...
Hello @kbullen, Sorry for having this issue, this is a known limitation. If you remove the SQL Clone machine, it will not remove the orphaned images, but you can follow the following workaround. 1. Delete all clones of the image. 2. Force delete the agent using the Remove-SqlCloneMachine PowerShell cmdlet. 3. Mark the image entry on database as deleted using the following SQL query. Before running the SQL query on your production environment, please test it on a testing environment in case that something will go wrong. UPDATE [dbo].Images SET DeletedOn = GETUTCDATE() WHERE Id = <b>{ImageId}</b>Please replace the {ImageId} with the actual image's id. 4. Delete the image from disk. Kind regards, Panagis / comments
Hello @kbullen,Sorry for having this issue, this is a known limitation.If you remove the SQL Clone machine, it will not remove the orphaned images, but you can follow the following workaround.1. De...
Hello @gemu. The permissions that you've set are fine. Here you can find more about the requirements. Regarding the concerns that you have with the UNC path, we are converting the UNC paths to local paths, so it's not an issue. The user account that runs the SQL Server service, doesn't need to have privileges on the shared location. There are two possible issues: 1. There isn't sufficient disk space on the shared location. 2. There is an issue when Windows tries to create or attach a Virtual Hard Disk (VHD) image. To test the last case, you can open the Disk Management (diskmgmt.msc) and try to create a VHD image by going to Action ---> Create VHD. The size of the VHD image should be roughly the same as the size of the database that you are trying to create an image from and the VHD type should be Dynamically expanding. After that you can try to attach the exported image by going to Action ---> Attach VHD. If any error occurs in the above process, then something goes wrong with the operating system. Kind regards, Panagis / comments
Hello @gemu.The permissions that you've set are fine. Here you can find more about the requirements.Regarding the concerns that you have with the UNC path, we are converting the UNC paths to local ...