Comments
Sort by recent activity
It's still unusable for us, even after an uninstall and reinstall. We don't use the default install location, but the physical path in IIS to the website folder is accurate. If it matters, the site is using "ApplicationPoolIdentity" credentials. / comments
It's still unusable for us, even after an uninstall and reinstall. We don't use the default install location, but the physical path in IIS to the website folder is accurate. If it matters, the site...
Yes, installing the latest update broke SQL Monitor for us too. The site is now offline and the logs are filled with errors such as this: 2020-04-08 20:34:40,953 [ 45] ERROR RedGate.SqlMonitor.Common.Utilities.ErrorReporting.RaygunErrorReporter - System.ArgumentNullException: String reference not set to an instance of a String. Parameter name: s at System.Text.Encoding.GetBytes(String s) at RedGate.SqlMonitor.Common.Persistence.CredentialsStore.CredentialManager.AddOrUpdate(String key, CredentialManagerDetails detail) at RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository.GetServiceAccountForDomain(String domain) at RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository.<GetAllConfigs>b__10_0(ValueTuple`2 tuple) at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext() at System.Linq.Buffer`1..ctor(IEnumerable`1 source) at System.Linq.Enumerable.ToArray[TSource](IEnumerable`1 source) at RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectoryConfigRepository.GetAllConfigs() at RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectory.ActiveDirectoryService.get_FirstConfig() at RedGate.SqlMonitor.Engine.Monitoring.Core.Services.ActiveDirectory.ActiveDirectoryConfigService.GetConfig()System.ArgumentNullException: String reference not set to an instance of a String. / comments
Yes, installing the latest update broke SQL Monitor for us too. The site is now offline and the logs are filled with errors such as this:2020-04-08 20:34:40,953 [ 45] ERRORRedGate.SqlMo...
Thanks for providing that link. I installed the update to version 10.0.8 and re-enabled the alert using its default values. We were immediately hit with around 100 "job duration unusual" alerts. I cleared those and lots of additional alerts are still coming in with various baseline deviations (-14%, -2%, 4%, 16%, 297%), all of which are under the threshold of 300% set in the configuration. Unfortunately, the fix doesn't appear to have worked for us. As for the configuration settings I mentioned, the same problem still exists in this version. The baseline deviation cannot be set above 100% like it could before. This prevents us from setting it to 200% for instance -- indicating the job is running twice as long as usual. The multiple alerts likewise can only be set to trigger between 0-100%. The only way I found to set it higher (300%) was to use the button to restore the default settings. Otherwise, the setting only lets me know that something is running longer than a fraction of the average, when the majority of the time we want to know if a job is running longer than the average. For the moment, we're going to have to disable the alert again. / comments
Thanks for providing that link.I installed the update to version 10.0.8 and re-enabled the alert using its default values. We were immediately hit with around 100 "job duration unusual" alerts. I c...
Alex B said:
In version 10.0.4 we made a change to allow the Job Duration Unusual (JDU) alert to fire while the job was still running, but unfortunately there were various issues with this that cause JDU alerts to fire in incorrect circumstances. The team are currently working on a fix under internal reference SRP-12900 for this and we will update here when that is available.
We definitely experienced this issue too when updating from version 10.0.3 to 10.0.7 yesterday and were forced to disable the alert until the problem is resolved. I'm glad to hear that a fix is forthcoming. As I cannot view the internal ticket, perhaps you're already aware of these three issues and working on them, but I thought it best to mention them just in case: 1. Alerts are triggering when jobs are running more quickly than the average (a negative baseline deviation). 2. Alerts are triggering for jobs from many months earlier stating that they never completed. 3. There is no way to modify the "Job Duration Unusual" alert thresholds for baseline deviation above 100% anymore (even though it defaults to 300%) in the configuration settings. / comments
Alex B said:
In version 10.0.4 we made a change to allow the Job Duration Unusual (JDU) alert to fire while the job was still running, but unfortunately there were various issues with this th...
Apologies. The initial forum post was accidentally submitted twice. Please feel free to lock or remove this double post. / comments
Apologies. The initial forum post was accidentally submitted twice. Please feel free to lock or remove this double post.
Since this was originally posted, I've been actively developing workarounds to the problem (mainly through the use of CSV files as reference documentation) and recently came across a similar situation regarding SQL Clone teams and permissions. There appear to be no SQL Clone PowerShell cmdlets that permit teams/permission management (e.g. creating/deleting a team, adding/removing a team assignment from a clone image or SQL Server location, etc.). Even more surprisingly, I found there is no way to determine team/permission assignments via PowerShell commands. There are no properties under the 'TeamsResource', 'ImageResource' or 'SqlServerInstanceResource' objects that indicate relationships between these objects. This is very similar to the deficiencies I previously noted for SQL Clone templates. As we attempt to automate clone refreshes, which include transferring templates and team-based permissions between images, it would be awesome if these relationships could be identified within PowerShell object properties and, especially in the case of team assignments, have some additional CLI options to manage them. Last I heard, my feedback was being discussed with the development team about a year ago: https://forum.red-gate.com/discussion/85836/perform-automatic-clone-database-refresh-with-templates I'm curious if there have been any updates since then that can be shared? Thanks. / comments
Since this was originally posted, I've been actively developing workarounds to the problem (mainly through the use of CSV files as reference documentation) and recently came across a similar situat...
Thanks for the response. We were hoping to avoid the idea of hardcoding clone-specific template script paths into our image/clone refresh scripts, but it sounds like that is our only option for now. We could better automate our clone refreshes if the 'CloneTemplateResource' object contained these properties (accessible using the 'Get-SqlCloneTemplate' cmdlet):
Filename. The original filename(s) of the modification script(s). Even if a full path is not stored, it would be nice to access the filename itself (like the GUI can) so that we can maintain a script location and match the existing template scripts to files there during clone refreshes.
SqlScript. The 'ModificationScript' objects associated with the template (whether it was originally imported from a file or passed as a string). Alternatively, a reference to 'ModificationScript' objects by ID that could be used with a 'Get-SqlCloneSqlScript' cmdlet to return a 'ModificationScript' object or the original script as a string value. These methods would allow the template script(s) to be captured as a variable and passed as a parameter during template creation for the new image.
Either of these options would better allow an image to be updated regularly and have all its clones refreshed without requiring change review and script revisions prior to every clone's initial creation. I hope this feedback will assist you in further improving the SQL Clone product. Thanks again.
/ comments
Thanks for the response. We were hoping to avoid the idea of hardcoding clone-specific template script paths into our image/clone refresh scripts, but it sounds like that is our only option for now...
@Russell D Our first attempt was an upgrade from 9.0.2 to 9.0.4. It failed and we reverted to 9.0.2. On our second attempt, we successfully upgraded from 9.0.2 to 9.0.3, but failed again from 9.0.3 to 9.0.4. We are sitting tight at version 9.0.3 for now. / comments
@Russell D Our first attempt was an upgrade from 9.0.2 to 9.0.4. It failed and we reverted to 9.0.2. On our second attempt, we successfully upgraded from 9.0.2 to 9.0.3, but failed again from 9.0.3...
We're experiencing the same issue as DonFerguson. No matter what we do, the 9.0.4 update fails during Base Monitor installation indicating an "insufficient privileges" error, but is actually due to a primary key violation in a new stored procedure called [datawarehouse].[PopulateAllRPOs]. Our [RedGateMonitor] database is also stored on SQL Server 2012. / comments
We're experiencing the same issue as DonFerguson.No matter what we do, the 9.0.4 update fails during Base Monitor installation indicating an "insufficient privileges" error, but is actually due to ...