Comments
Sort by recent activity
In your Compare project, you can set up a table mapping, and inside that map the source and target columns. Compare will then understand that the correct scripting behaviour is to rename the column and then change the column type (rather than doing a drop and recreate, with resulting data loss) / comments
In your Compare project, you can set up a table mapping, and inside that map the source and target columns. Compare will then understand that the correct scripting behaviour is to rename the column...
Hi James, We have logged this as case SC-10433 and will investigate for you. It may be worth trying a more recent release - 13.6.11 is available for download. Best wishes, Julia / comments
Hi James,We have logged this as case SC-10433 and will investigate for you. It may be worth trying a more recent release - 13.6.11 is available for download.Best wishes,Julia
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...