microsoft / microsoft/sqlmanagementobjects
Extended properties not supported on Azure Sql? Is there a plan to support?
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Hi all,
Im using SMO to generate a database and related objects on an Azure Sql server (fully hosted not a VM or Sql Managed Instance). I can generate objects such as tables, indexes, stored procedures and views but I cannot create extended properties associated with these objects. This works perfectly on my local sql server. As a result of this problem I have had to add my own extended property script generators which has exploded the code base. Any plans to correct this in the future?
Thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by locating SMO's extended-property generation path and its Azure SQL capability handling, then compare the behavior with local SQL Server. Done means extended properties can be created for the stated Azure SQL objects, with regression coverage.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, csharp, sql
- Domain
- cloud, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100