Comments
Sort by recent activity
SQL Monitor 9.1.7 has been released. Direct download link Features
SRP-12324 Estates pages use dynamic unit selection for memory usage
SRP-12315 Added PowerShell example script for copying alert settings between monitored objects through API
Fixes
SRP-12278 Clear backup overdue alerts when they are present on a secondary node
SRP-12293 Fix issue with enumerating some AD groups in permissions sampler
SRP-12112 The error that appears when a base monitor that has been added cannot be reached has been fixed
SRP-12343 An issue that could lead to custom metrics incorrectly displaying as being disabled has been fixed
/ comments
SQL Monitor 9.1.7 has been released. Direct download linkFeatures
SRP-12324 Estates pages use dynamic unit selection for memory usage
SRP-12315 Added PowerShell example script for copying alert ...
SQL Monitor 9.1.3 has been released. Direct download link. Features SRP-12222 Hashing algorithms are now FIPS compliant SRP-12183 Ignore sp_server_diagnostics in long-running query alert SRP-12200 Added new analysis graph metrics for SQL Server memory 145129 Display seconds on times in long-running query alert SRP-12232 Added support for base monitor error notification email address configuration Added initial support for the retrieval and update of Alert Specific Settings for the following alert types: DatabaseFileUsage, AvailabilityGroupDelayedQuery, AvailabilityGroupReplicaFallingBehind, LowDiskSpaceAlerter, LowMemorySpaceAlerter, SqlDeadlockXE and DatabaseSizeAzureSqlDb. Further alert types will be supported in upcoming releases. Fixes SRP-12254 Reduce frequency of AD queries for user running base monitor process SRP-12000 Fixed an issue where the authentication type page could show incorrect information on multiple base monitor environments SRP-12253 Fixed an issue where the server summary report failed to load data / comments
SQL Monitor 9.1.3 has been released. Direct download link.FeaturesSRP-12222 Hashing algorithms are now FIPS compliantSRP-12183 Ignore sp_server_diagnostics in long-running query alertSRP-12200 Adde...
Hi, Unfortunately SQL Clone doesn't support PaaS version of Azure SQL. Is it possible for you to mention about your use case? Thanks / comments
Hi,Unfortunately SQL Clone doesn't support PaaS version of Azure SQL. Is it possible for you to mention about your use case?Thanks
Hi, When you run Get-SqlClone, cmdlet returns you a CloneResource object which includes LocationId. But the problem is, it is not possible to get the SqlServerInstance by using this LocationId. A basic solution is, you can query all Sql Server Instances by using Get-SqlCloneSqlServerInstance and you can try to find the LocationId in the result of Get-SqlCloneSqlServerInstance. You can find an example query below. Connect-SqlClone -ServerUrl 'http://your_sql_clone_server_url'
$clone = Get-SqlClone -Name 'your_clone_name' $cloneLocationId = $clone.LocationId $sqlServerInstances = Get-SqlCloneSqlServerInstance foreach($instance IN $sqlServerInstances) { if($instance.Id -eq $cloneLocationId) { Write-Output $instance } } / comments
Hi,When you run Get-SqlClone, cmdlet returns you a CloneResource object which includes LocationId. But the problem is, it is not possible to get the SqlServerInstance by using this LocationId. A ba...
Hi,
While using Get-SqlClone with Name and Location parameters, you make an exact search for clone. So, if there is no clone with given credentials, you will receive an error. To avoid this, there are two ways:
1. Using try catch
2. Getting all clones of a specific location and try to get your clone name from this list by using powershell
(Get-SqlClone -Location $SqlServerInstance)
There are 2 more usage of Get-SqlClone command. (But these usages can cause to delete more clones on your environment)
1. You can use wildcard (*) with your clone name. For example: Get-SqlClone -Name 'clone_name*' -Location $SqlServerInstance
With this command, you will receive all clones which starts with "clone_name" for the location you specified. If there is no clone starts with "clone_name", there will be no error message and you will receive null object.
2. You can use Get-SqlClone command without using "Location" parameter. This usage, will return all clones with specified clone name regardless of location. If there is no clone with specified name, there will be no error message and you will receive null object.
Best Regards / comments
Hi,
While using Get-SqlClone with Name and Location parameters, you make an exact search for clone. So, if there is no clone with given credentials, you will receive an error. To avoid this, there ...
Hi,
Your script seems correct. To better investigate the problem, could you send the error message you receive and installed SQL Clone version?
Thanks. / comments
Hi,
Your script seems correct. To better investigate the problem, could you send the error message you receive and installed SQL Clone version?
Thanks.
Hi Benethor,
You can use the below script to get the machine name and environment from a clone.
Connect-SqlClone -ServerUrl 'http://your_sql_clone_domain:14145'
$clone = Get-SqlClone -Name your_clone_name
$locationId = $clone.LocationId
$sqlServerInstance = Get-SqlCloneSqlServerInstance | where {$_.Id -eq $clone.LocationId}
$sqlServerInstance.Machine / comments
Hi Benethor,
You can use the below script to get the machine name and environment from a clone.
Connect-SqlClone -ServerUrl 'http://your_sql_clone_domain:14145'
$clone = Get-SqlClone -Name your_clo...
Hi
You can find the logs by following instructions in here / comments
Hi
You can find the logs by following instructions in here
Hi Mattias,
Thank you for your feedback. A new powershell cmdlet (Get-SqlCloneMachine) has been implemented and released in version SQL Clone 2.3.
Get-SqlCloneMachine returns the details of machines from SQL Clone Server. You can get the details of cmdlet here. / comments
Hi Mattias,
Thank you for your feedback. A new powershell cmdlet (Get-SqlCloneMachine) has been implemented and released in version SQL Clone 2.3.
Get-SqlCloneMachine returns the details of machine...