microsoft / microsoft/sqlmanagementobjects
Sql Management Objects async overloads
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
(Please let me know if this is the wrong repo)
I was pleasantly surprised to find SMO is staying up-to-date with the latest features of SQL Server and is available on .NET Core.
One area in which its sorely lacking, however is in async support. async/await has been in the C# language since 2012; Async overloads are crucial in nearly every framework doing I/O in .NET.
SMO should add Async overloads for any method call that results in a call to the database. This is important so that a thread is not just sitting there, blocked and idle, while waiting on an external operation.
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
No file, test, or entry point is named. Start by surveying SMO methods that issue database calls and determine the scope of async overloads; done means the applicable calls have async/await-capable overloads without blocking a thread, with coverage verified by the project’s existing tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend-api-design, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100