microsoft / microsoft/sqlmanagementobjects
"Model" database size is read by transfer when not creating a database.
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 143
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
When using the Transfer object to clone a database catalog into an existing empty database, DataTransferBase invokes SetTargetServerInfoAndGetModelSize() and reads the size of the "model" database. This is unnecessary and actually unwanted due to the fact that this seems to place an exclusive lock on the "model" database.
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
Start with the Transfer flow and trace DataTransferBase's call to SetTargetServerInfoAndGetModelSize(). Confirm why cloning into an existing empty database reads the model database and whether that creates the unwanted exclusive lock. The issue names no source file or test; done means the unnecessary model-size read no longer occurs in this scenario.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100