Comments
Sort by recent activity
Hi Sergio, Will this method also work if I want to remove the web server from another combined installation and re-add the base monitor this time as a secondary base monitor? / comments
Hi Sergio,Will this method also work if I want to remove the web server from another combined installation and re-add the base monitor this time as a secondary base monitor?
Hi Dan, I just checked now, no the tiles are still there. So it is likely to be the web and | or base monitor versions that may be that its not supported in the current version. / comments
Hi Dan,I just checked now, no the tiles are still there. So it is likely to be the web and | or base monitor versions that may be that its not supported in the current version.
Hi Alex, my colleague wrote the powershell and the team looked over it and it worked. The All servers level was disabled for differential backup when the powershell script was run. After it ran it impacted settings on all servers under all base monitors at the system db level. All dbs we do want to monitor remained at inherited. When differential was enabled at all servers level it worked as desired. / comments
Hi Alex, my colleague wrote the powershell and the team looked over it and it worked. The All servers level was disabled for differential backup when the powershell script was run. After it ran it ...
Thanks for this Alex. I will look into the powershell option now. Kind Regards Phil / comments
Thanks for this Alex. I will look into the powershell option now.Kind Regards Phil
I successfully moved the RedGateMonitor Database from Azure SQL Server VM to Azure SQL DB. It is a slow process. You have to generate a backpac file within SSMS and upload to blob storage (Its best to suspend the Base Monitor Service while this takes place as it speeds up the process), and then import the Bacpac file as a new DB (Azure SQL Database does not allow you to overwrite an existing database with the same DB name as that in the Backpac file the new database has to be made from it) The import process is best left overnight as it is slow. The only other alternative that could have been used is Deploy to Azure SQL Server which I have not tested. I then re-pointed the server to the web address of the Azure SQL DB in the config file. RedGate.SqlMonitor.Engine.Alerting.Base.Service.exe.settings.config Data Source=MACHINENAME\SQLInstancename Change to Data Source = Web address of Azure SQL DB / comments
I successfully moved the RedGateMonitor Database from Azure SQL Server VM to Azure SQL DB.It is a slow process. You have to generate a backpac file within SSMS and upload to blob storage (Its best ...