microsoft / microsoft/go-sqlcmd
Provide ability to direct restore a URL (with a CREDENTIAL) instead of copying to container first
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
Right now the sqlcmd use functionality copies the file to the container, and then before the action to restore/attach etc.
This comment in a code review suggests we enable the ability to restore the URL directly from the sqlservr process in the container (avoiding the need for the copy to container)
"for .bak files using a URL we should provide a way to create a CREDENTIAL to store on the server so it can restore directly from the URL.
SQL 2022 supports both https and s3 URLs"
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 by tracing the sqlcmd use entry point and how it currently copies URL-based .bak files into the container before restore or attach. Define how a CREDENTIAL is created and supplied to the SQL Server process for HTTPS and S3 URLs, then verify that restore can read directly from the URL without the container copy.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, sql
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100