Update alter-database-transact-sql.md

[charithcaldera]

ALTER DATABASE MODIFY NAME does not work with Azure Synapse Analytics Dedicated SQL Pool
Test Scenario - Rename SQL Pools.docx
s

[PRMerger-2]

@charithcaldera : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[WilliamDAssafMSFT]

@charithcaldera Does this apply to both legacy standalone dedicated SQL pools (formerly SQL DW) and dedicated SQL pools in Azure Synapse workspaces?

[charithcaldera]

Hi @WilliamDAssafMSFT ,
ALTER DATABASE MODIFY NAME works for Legacy standalone Dedicated SQL Pools (formerly SQL DW), but it does not work for Dedicated SQL Pools in Azure Synapse workspace.
Document attached.
Test Scenario - Rename SQL Pools.docx

[jborsecnik]

@WilliamDAssafMSFT, if you approve the changes, please add a #sign-off comment to signal that the PR is ready for the review team to merge. Thanks.

#label:"aq-pr-triaged"

[WilliamDAssafMSFT]

Hi @WilliamDAssafMSFT , ALTER DATABASE MODIFY NAME works for Legacy standalone Dedicated SQL Pools (formerly SQL DW), but it does not work for Dedicated SQL Pools in Azure Synapse workspace. Document attached. Test Scenario - Rename SQL Pools.docx

Based on that information the article is accurate. The comments on line 1044 are specific as to what scenarios ALTER DATABASE MODIFY NAME is supported. These changes as proposed would be too broad, as ALTER DATABASE MODIFY NAME is supported in some dedicated SQL pools.

[charithcaldera]

@WilliamDAssafMSFT ,
This appears to be making a confusion here,

Azure Synapse SQL Dedicated Pool and Standalone Dedicated Pools (Formerly SQL DW) are treated as two.

In this public document, in line 966, its mentioned as follows which can make a confusion -
"In Azure Synapse, ALTER DATABASE modifies the name, maximum size, or service objective for a database."

Since Azure Synapse Analytics Dedicated SQL Pools does not supported on "ALTER DATABASE MODIFY NAME" according to line 1046, the two lines (966 and 1046) having a conflict there.

The problem is not about the Standalone Dedicated Pools (Formerly SQL DW), but the Dedicated Pools in Azure Synapse Workspace.
I hope its clear.

[WilliamDAssafMSFT]

I understand. I've updated the line near the top of the article to be more general. I've reverted the change on line 966. Please commit these two Suggestions, thanks!

[PRMerger20]

@charithcaldera: I'm sorry - only the author of this article, @WilliamDAssafMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

[charithcaldera]

Thank you @WilliamDAssafMSFT ,
I agree with your suggestions / changes.

[WilliamDAssafMSFT]

#hold-off
@charithcaldera you should see options beneath each of my suggestions to "Commit suggestion". Go ahead and commit those changes. You'll know for sure they're in when they are reflected in the Files Changed tab.

[PRMerger14]

@charithcaldera : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[PRMerger19]

@charithcaldera : Thanks for your contribution! The author(s) have been notified to review your proposed change.

[charithcaldera]

Hi @WilliamDAssafMSFT ,
Done

[WilliamDAssafMSFT]

Thanks @charithcaldera!!
#sign-off