Comments
Sort by recent activity
Hello, Thank you for your inquiry into SQL Monitor. Unfortunately, there is no way of exporting the SQL Server Licensing(Estate) to a SQL table instead of a spreadsheet from SQL Monitor. It may be possible to import from xls doc to SQL table (or save the xls as csv which may be easier to import to SQL). https://docs.microsoft.com/en-us/sql/relational-databases/import-export/import-data-from-excel-to-sql?view=sql-server-ver16 I hope this information helps. Best, Dustin / comments
Hello,Thank you for your inquiry into SQL Monitor.Unfortunately, there is no way of exporting the SQL Server Licensing(Estate) to a SQL table instead of a spreadsheet from SQL Monitor.It may be pos...
Hello, Unfortunately, there is no simple way of disabling the alerts during off-peak hours as there is nothing built in by default to do this. The couple options that may be possible are. To use the PowerShell API on a schedule to disable the alert during off-peak hours and re-enable it when peak hours start. This is probably the best option as the data will be collected throughout and it is just the alert that is disabled. Though this may not work with custom alerts. Apart from that would be setting fake values in the SQL which you stated you are wanting to avoid, but adding +1 to any data in the off-peak hours so that it would always be at least 1 and just understand during offpeak hours it shows 1 more than it actually is ( the custom alert will need to be set up to fire when the value crosses the threshold 1). I hope this information helps. Best, Dustin / comments
Hello,Unfortunately, there is no simple way of disabling the alerts during off-peak hours as there is nothing built in by default to do this. The couple options that may be possible are. To use the...
Hi Surya, There were recent changes to the way information is exported to excel during the latest release but it looks to be just the way BIGINT is handled. 10.12.3.28623 - Released on 29 July 2022 Fixes
Fixed an issue where BIGINT data types were being exported to Excel in scientific notation.
Fixed a performance issue where typing in SSMS was laggy when large snippets are present.
Fixed an issue with an incorrect execution warning when using the ALTER TABLE syntax.
Added support for some SQL Server 2022 syntax, including LEDGER.
Fixed a crash that could occur when running the command line formatter.
What is the DataType that is being exported as text to excel so we can attempt to recreate it on our end? Best, Dustin / comments
Hi Surya, There were recent changes to the way information is exported to excel during the latest release but it looks to be just the way BIGINT is handled.10.12.3.28623 - Released on 29 July 2022F...
Hello, Unfortunately, it does not appear that SQL Prompt has the level of customization available to remove the spaces between the values. We are always looking for suggestions for new features and welcome you to add this as a recommendation for our development team to look into in our user's voice forum. https://redgate.uservoice.com/forums/94413-sql-prompt Best, Dustin / comments
Hello,Unfortunately, it does not appear that SQL Prompt has the level of customization available to remove the spaces between the values.We are always looking for suggestions for new features and w...
Hi Richard, Thank you for your inquiry into SQL Clone. You may be running into a limitation with SQL Clone when attempting to make modifications: "The scripts will be run with limited privileges - as a temporary user which only has permission to modify the image as db_owner, not to make changes to the server or to other databases." https://documentation.red-gate.com/clone/modifications-during-provisioning/image-modifications/t-sql-modifications I hope this information helps. Best, Dustin / comments
Hi Richard, Thank you for your inquiry into SQL Clone. You may be running into a limitation with SQL Clone when attempting to make modifications:"The scripts will be run with limited privileges - a...
Hi Richard, Thank you for your inquiry into SQL Source Control. The article below gives advice and steps on migrating to Azure DevOps: https://www.dotnetcurry.com/devops/1540/code-migration-azure-devops I hope this information helps. Best, Dustin / comments
Hi Richard,Thank you for your inquiry into SQL Source Control.The article below gives advice and steps on migrating to Azure DevOps:https://www.dotnetcurry.com/devops/1540/code-migration-azure-devo...
Hi Aaron, Thank you for your inquiry into SQL Prompt we are sorry to hear it is giving you trouble. We unfortunately were unable to replicate the issue on our end regarding the tabs not being the correct color when connected to a database using SSMS 18.12.1 and SQL Prompt 10.12.2 and may need a little more information to hopefully narrow down the issue. We have opened a case and sent an email to inquire for further information. Best, Dustin / comments
Hi Aaron,Thank you for your inquiry into SQL Prompt we are sorry to hear it is giving you trouble.We unfortunately were unable to replicate the issue on our end regarding the tabs not being the cor...
HI Craig, Thank you for your inquiry into SQL Source Control. The article below may help with the git error you are seeing: https://github.com/actions/checkout/issues/766
Workaround: Other steps are failing
Since we don't persist that configuration, you may still see this error if your job uses git commands outside of the checkout action. If so, you just need to set the configuration value yourself.
Simply set the GITHUB_WORKSPACE as a safe directory.
git config --global --add safe.directory "$GITHUB_WORKSPACE"
If your github workspace starts off with // , you may need to set it via
git config --global --add safe.directory "%(prefix)/$GITHUB_WORKSPACE"
A little more detail about setting a safe repository is located here: https://git-scm.com/docs/git-config/#Documentation/git-config.txt-safedirectory I hope this helps. Best, Dustin / comments
HI Craig, Thank you for your inquiry into SQL Source Control. The article below may help with the git error you are seeing:https://github.com/actions/checkout/issues/766
Workaround: Other steps ar...
Hi Chris, Thank you for checking that, we may need more information on this one since we can no longer replicate this scenario on our end and will be reaching out via email. Best, Dustin / comments
Hi Chris,Thank you for checking that, we may need more information on this one since we can no longer replicate this scenario on our end and will be reaching out via email.Best,Dustin
Hi Chris, We were able to reproduce the formatting problem as described. We have escalated this to our dev team for further investigation and will follow up once more information has been made available. Best, Dustin / comments
Hi Chris,We were able to reproduce the formatting problem as described.We have escalated this to our dev team for further investigation and will follow up once more information has been made availa...