Skip to content

qualify sp_renames support in Azure Synapse#6793

Merged
ktoliver merged 2 commits intoMicrosoftDocs:livefrom
dataders:patch-2
Nov 9, 2021
Merged

qualify sp_renames support in Azure Synapse#6793
ktoliver merged 2 commits intoMicrosoftDocs:livefrom
dataders:patch-2

Conversation

@dataders
Copy link
Copy Markdown
Contributor

@dataders dataders commented Sep 8, 2021

sp_rename is supported for dedicated pools, just not serverless SQL pools

questions

  • is sp_rename only supported for the dbo schema of all databases of the Built-In Serverless pool? or just the default?
  • should I have used this snippet instead?
    [!INCLUDE[synapse-analytics-od-unsupported-syntax](../../includes/synapse-analytics-od-unsupported-syntax.md)]

sp_rename is supported for dedicated pools
@PRMerger13
Copy link
Copy Markdown
Contributor

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

@rothja
Copy link
Copy Markdown
Collaborator

rothja commented Sep 21, 2021

@swanderz Anders, thanks for the suggestion, and I apologize for the delay. @julieMSFT Julie, could you please take a look at this PR? #reassign:juliemsft

@PRMerger7 PRMerger7 assigned julieMSFT and unassigned markingmyname Sep 21, 2021
@julieMSFT
Copy link
Copy Markdown
Contributor

@swanderz sp_rename is supported in serverless SQL pool. It is in preview for dedicated SQL pool. Can you update your updates to dedicated SQL pool.

@dataders
Copy link
Copy Markdown
Contributor Author

dataders commented Oct 4, 2021

@swanderz sp_rename is supported in serverless SQL pool. It is in preview for dedicated SQL pool. Can you update your updates to dedicated SQL pool.

thanks for getting back to me! I might be wrong here, but I think you have it reversed, as least as far as renaming views is concerned? In a serverless pool I cannot rename a view, but in a dedicated pool I can. Happy to provide a reproducible example if need be.

Comment thread docs/relational-databases/system-stored-procedures/sp-rename-transact-sql.md Outdated
Comment thread docs/relational-databases/system-stored-procedures/sp-rename-transact-sql.md Outdated
@julieMSFT
Copy link
Copy Markdown
Contributor

@swanderz Sorry for the confusion. You are correct sp_rename is in preview for dedicated SQL pool. It is not supported in serverless SQL pool. If you make the updates to this PR we can get it merged.

Co-authored-by: julieMSFT <44736634+julieMSFT@users.noreply.github.com>
@PRMerger5
Copy link
Copy Markdown
Contributor

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

Copy link
Copy Markdown
Contributor Author

@dataders dataders left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

thanks for getting back @julieMSFT! my only pushback was that the whole reason I opened this PR was trying to save people the time I wasted trying to get sp_rename working on serverless pools. Is there anywhere on this page today that tells warns someone that they shouldn't use sp_rename on serverless pools today?

@dataders dataders requested a review from julieMSFT November 9, 2021 23:39
@julieMSFT
Copy link
Copy Markdown
Contributor

@swanderz Thank you for make the update so quickly. I will get this merged. I will also add a note that sp_rename does not work for serverless SQL pools.

@julieMSFT
Copy link
Copy Markdown
Contributor

#sign-off

@PRMerger8
Copy link
Copy Markdown
Contributor

@julieMSFT: I'm sorry - only the author of this article, @markingmyname, 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.

@ktoliver ktoliver merged commit 6cb495b into MicrosoftDocs:live Nov 9, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants