Open viniciusvillas opened 4 years ago
Thanks for the feedback! We are routing this to the appropriate team for follow-up. cc @azureSQLGitHub.
Thanks for reporting. SQL team, please help to look into this issue.
JSYK, I was able to replicate this exactly behavior on three different machines. It doesn't seem like an environment issue.
Any update on this? Our script is still broken.
Hello guys! Could anyone give us an update about this issue? Will it be solved? Will it be dismissed? Is this feature being deprecated? I'm just after an indication to decide whether to steer our efforts towards some other solution or just wait. Thanks! ;)
Issues here as well. and have databases with 27000 entries that need remediated. the limit of 100 in the portal is not gonna cut it.
Having this same issue with Get-AzSqlDatabaseSensitivityRecommendation. Runs fine locally but fails in an Azure PowerShell task in AzDO with 404.
The fix for this is to install Az.sql version 2.6.0- Install-Module Az.sql -RequiredVersion 2.6.0 -SkipPublisherCheck -force -AllowClobber Then import it Import-module Az.Sql -RequiredVersion 2.6.0 Run the commands using e.g Set-AzSqlDatabaseSensitivityClassification
Reverting to Az.Sql 2.6.0 worked for me as well. Not exactly ideal.
Got same error message while trying to disable sensitivity recommendations with: Get-AzSqlDatabaseSensitivityRecommendation -ResourceGroupName resourceGroup -ServerName server -DatabaseName database | Disable-AzSqlDatabaseSensitivityRecommendation Get-AzSqlDatabaseSensitivityRecommendation works fine, but Disable-AzSqlDatabaseSensitivityRecommendation part do not work. Az.SQL version : 3.3.0
The fix for this is to install Az.sql version 2.6.0- Install-Module Az.sql -RequiredVersion 2.6.0 -SkipPublisherCheck -force -AllowClobber Then import it Import-module Az.Sql -RequiredVersion 2.6.0 Run the commands using e.g Set-AzSqlDatabaseSensitivityClassification
Thank you!!! Been struggling to set all 10000 + Sensitivity Classifications for a database 2 days now, and the revert to Az.sql 2.6.0 worked for me too. The accept only 100 at a time in the Portal UI definitely not going to cut it....
@viniciusvillas Apologies for the delayed response. I see that this issue is opened long time ago and no further activity had taken place. So wanted to check if you are still looking for assistance on this query? Please let us know .
Hi, we're sending this friendly reminder because we haven't heard back from you in a while. We need more information about this issue to help address it. Please be sure to give us your input within the next 7 days. If we don't hear back from you within 14 days of this comment the issue will be automatically closed. Thank you!
@viniciusvillas Apologies for the delayed response. I see that this issue is opened long time ago and no further activity had taken place. So wanted to check if you are still looking for assistance on this query? Please let us know .
Hi Sharma! Thanks for the reply! Better late than never, I think ;) I've been using the REST interface - I copied the calls from the Azure Portal - to dismiss these classification suggestions, so I can't say if this is fixed or not on the cmdlet. To be honest, I lost faith that this would ever be responded - which is odd, given the size of the company behind Azure and the annual profit they get from it, bugs should be high in their priority list. This was 1 and 1/2 years ago, so it really should be fixed by now, regardless of my own necessity. Thanks, nonetheless!
Just posting that this is still an issue in the latest version of Az. Installing 2.6.0 fixed the issue.
Now we have so many advance versions of Az.sql , then why only it works with 2.6.0?
Description
The calls to the cmdlet
Remove-AzSqlDatabaseSensivityClassification
always fails with the error message:Steps to reproduce
Just call the cmdlet as shown in the documentation. Both modes (passing the ClassificationObject parameter or the standalone parameters - resouce group name, database name, schema, table, etc) results in the same error message.
Environment data
Module versions
Debug output
Error output