Comments
Sort by recent activity
Just to clarify a little, it's SQL Server itself that automatically converts all mentions of [rowversion] to [timestamp] at the point where it parses DDL queries - if you create a table with a [rowversion] column and then ask SQL to script that table out, you'll see it has done the conversion automatically. And this query: SELECT * FROM sys.types WHERE name = N'rowversion'<span>;</span>returns no rows. It's clearly an unsatisfactory situation that the automatic conversion is done *to* the deprecated one, and won't be resolved until a SQL is released where the conversion is reversed. / comments
Just to clarify a little, it's SQL Server itself that automatically converts all mentions of [rowversion] to [timestamp] at the point where it parses DDL queries - if you create a table with a [row...
Hi Cristy, Other than the inconsistency in the number saved in the .sqlgen file, could you describe the problems that not running all the scripts causes you? I believe that when you run the data generation, the incorrect RowCount field for each of the Python generators is updated to the number of rows requested for the table in any case, and so the RowCount entry in the .sqlgen file specific to the generator is actually redundant? Best wishes, Julia Hayward Technical Lead, SQL Toolbelt / comments
Hi Cristy,Other than the inconsistency in the number saved in the .sqlgen file, could you describe the problems that not running all the scripts causes you? I believe that when you run the data gen...
You can achieve the same effect via the Server Options dialog: check `Delete all backup and restore history older than XX days`. / comments
You can achieve the same effect via the Server Options dialog: check `Delete all backup and restore history older than XX days`.
The next issue we're working on is bulk uninstallation of our products - this comes up a lot in feedback as a particularly painful experience for people who install the whole toolbelt. SQL Doc is in the process of releasing with an integrated uninstaller right now, and it will roll out across the suite in the coming days. / comments
The next issue we're working on is bulk uninstallation of our products - this comes up a lot in feedback as a particularly painful experience for people who install the whole toolbelt. SQL Doc is i...
@kkam99518 At the moment we're releasing the new installer for single products. As soon as this rollout is done we're moving on to the full Toolbelt installers - which will show you all available updates separately from new products and allow you to do them en masse. Hopefully this will improve your experience. / comments
@kkam99518 At the moment we're releasing the new installer for single products. As soon as this rollout is done we're moving on to the full Toolbelt installers - which will show you all available u...
Hi Darek,
Many thanks for your feedback. We will have a look at all of points you've raised when we next do work on SQL Test - if there are any other enhancements you'd like, please do let us know.
Best wishes,
Julia
(SQL Toolbelt team) / comments
Hi Darek,
Many thanks for your feedback. We will have a look at all of points you've raised when we next do work on SQL Test - if there are any other enhancements you'd like, please do let us know....
Thanks for your feedback, everyone. We're currently assessing the best way to resolve this issue - hopefully we'll be able to get back to you soon. / comments
Thanks for your feedback, everyone. We're currently assessing the best way to resolve this issue - hopefully we'll be able to get back to you soon.
SQL Monitor 6.0.2 has now been released.
This has a number of fixes for support cases:
SRP-10790 Customised custom alert settings are lost after re-saving the metric
SRP-10791 Changed description for custom alert doesn't appear in email
SRP-10807 Upgrade changes the webserver port, if installed while SQM is running
SRP-10811 Unable to scroll Top Waits list / comments
SQL Monitor 6.0.2 has now been released.
This has a number of fixes for support cases:
SRP-10790 Customised custom alert settings are lost after re-saving the metric
SRP-10791 Changed description f...
SQL Monitor 6.0.3 has been released today.
This release contains an early beta version of reporting functionality plus a sample integration with PowerBI. We've re-enabled Intercom specifically on this page and we welcome feedback to help us plan the future direction of reporting. We have also added fixes for a number of support cases:
SRP-10845/7 Server Overview sparkline formatting enhancements
SRP-10835 Server Overview log entries are truncated by default, but can be expanded if the full text is needed.
SRP-10834 Server Overview database count could give wrong value in Edge browser
SRP-10833 Server Overview top queries scrolling issue in Internet Explorer 11
SRP-10825 Server Overview database list can now be filtered
SRP-10435 Base Monitor service does not start cleanly when data repository is unavailable
SRP-9636 Base Monitor should cause fewer deadlocks when purging data
SRP-7482 On following old links in emails to purged alerts, more helpful information is given / comments
SQL Monitor 6.0.3 has been released today.
This release contains an early beta version of reporting functionality plus a sample integration with PowerBI. We've re-enabled Intercom specifically on t...
SQL Monitor 6.0.7 has been released. This version features a number of minor enhancements, including:
- beta support for Slack and SNMP integration for alert notifications, in addition to email.
- Query execution plans can be exported in .sqlplan format
- The database table search can now be cleared.
- 12/24 hour clock display of dates is now consistent and can be toggled from a new Display Options page
It also resolves the following support issue:
SRP-10854 Fragmented index alerts firing on database snapshots / comments
SQL Monitor 6.0.7 has been released. This version features a number of minor enhancements, including:
- beta support for Slack and SNMP integration for alert notifications, in addition to email.
- ...