Comments
Sort by recent activity
SQL Monitor 10.2.1 has been released. Direct download link
Breaking Changes
Starting with SQL Monitor v10.2, SQL Monitor base monitors can no longer be installed on Windows Server 2012 or earlier. For the time being, this only affects the base monitor. Support for running the SQL Monitor website on Windows Server 2012 or earlier will be removed in the future.
We've moved to .NET Core 3.1; Microsoft do not support Windows Server 2012 or earlier as deployment targets for .NET Core 3.1. This also means that SQL Monitor base monitors cannot be installed on unsupported desktop operating systems. Refer to Microsoft's installation guidance for specific versions.
You can monitor the same versions of Windows and SQL Server that you've always monitored. However, base monitors need to be installed on Windows Server 2012 R2 or newer.
Features The Amazon RDS SQL Server monitoring preview now includes support for alerts and groups.
Most SQL Server-specific alerts can now be raised for Amazon RDS SQL Servers.
The alerts appear in the alert inbox, and alert summaries appear in the global and server overview pages.
Amazon RDS SQL Servers can now be placed into groups.
Alert settings for each server are inherited from their group, and can be overridden in the Configure > Alert settings pages.
Fixes
SRP-13298 fixed an issue loading log pages for clusters or cluster nodes.
Correctly display warning when upgrading from a version of SQL Monitor earlier than 10.2 that installing on older Windows versions is no longer supported.
/ comments
SQL Monitor 10.2.1 has been released. Direct download link
Breaking Changes
Starting with SQL Monitor v10.2, SQL Monitor base monitors can no longer be installed on Windows Server 2012 or earlier...
@InkZ, @brookal , we've just released a version that fixes the regression (3.0.18331). Once again sorry for the inconvenience caused. If it's not a big problem, could you please check what version of .NET Framework is installed on machines where your builds were failing? Regarding support for Shadow Database on Azure, we currently don't support such a scenario indeed, but actively working on improving it as we speak. For more info please see this help page. / comments
@InkZ, @brookal , we've just released a version that fixes the regression (3.0.18331). Once again sorry for the inconvenience caused.If it's not a big problem, could you please check what version o...
Actually, I've taken a second look, and in your case, pinning the version is not possible, because you use "Visual Studio Build" rather than "Redgate SQL Change Automation Build". The versions to be put in this box are versions listed here: https://www.powershellgallery.com/packages/SqlChangeAutomation/3.0.1.2275, but in this case the "lastest" version would work fine. It looks like you use local agents, so on these machines, you can just install the version 3.0.18324, however the recommended way would be to change your build definition to use the "Redgate SQL Change Automation Build" task. / comments
Actually, I've taken a second look, and in your case, pinning the version is not possible, because you use "Visual Studio Build" rather than "Redgate SQL Change Automation Build". The versions to b...
Sam, we're going to release a fix tomorrow. As a temporary workaround, you can pin to a specific version of SQL Change Automation in Azure DevOps: [image] / comments
Sam, we're going to release a fix tomorrow.As a temporary workaround, you can pin to a specific version of SQL Change Automation in Azure DevOps:
I assume you clicked the Refresh button in the middle of the screen (between "Add tasks" and the search box)? For me it looks like this: [image] Maybe you need not only to install it, but also add it to your organization? / comments
I assume you clicked the Refresh button in the middle of the screen (between "Add tasks" and the search box)? For me it looks like this:Maybe you need not only to install it, but also add it to you...
Hi Alan, sorry for the inconvenience caused. It's a regression introduced in the latest release 3.0.18326. We're working on a fix and going to release a new version soon. / comments
Hi Alan, sorry for the inconvenience caused. It's a regression introduced in the latest release 3.0.18326.We're working on a fix and going to release a new version soon.
You need to edit your sqlproj file and set the options manually. For more detailed guidance and additional information please see the documentation: Configuring comparison & script generation options. / comments
You need to edit your sqlproj file and set the options manually. For more detailed guidance and additional information please see the documentation: Configuring comparison & script generation options.
We were able to identify the root cause of this issue and we're working on a permanent fix. For now, a workaround is to add the following line into a PropertyGroup in the .sqlproj: <SyncOptionIgnoreConstraintNotForReplicationAttribute>False</SyncOptionIgnoreConstraintNotForReplicationAttribute>Sorry for the inconvenience caused. For the future reference, regarding creating support tickets, please start from the https://productsupport.red-gate.com/hc/en-us page , where you can submit a request. / comments
We were able to identify the root cause of this issue and we're working on a permanent fix.For now, a workaround is to add the following line into a PropertyGroup in the .sqlproj:<SyncOptionIgnoreC...
Hi Roman, I'm just releasing a new version of the product with extended logging, the version number is 3.0.18283. Could you please install this version and provide the logs again? Sorry for the inconvenience caused. Actually, if you could file a support ticket, we could provide you with better assistance. / comments
Hi Roman, I'm just releasing a new version of the product with extended logging, the version number is 3.0.18283.Could you please install this version and provide the logs again?Sorry for the incon...
Hi Roman, could you paste these 2 lines from the log file between which a gap occurs? It seems that you've found the logs yourself, for future reference they're stored in %localappdata%\Red Gate\Logs\SQL Change Automation / comments
Hi Roman, could you paste these 2 lines from the log file between which a gap occurs?It seems that you've found the logs yourself, for future reference they're stored in %localappdata%\Red Gate\Log...