microsoft / microsoft/go-sqlcmd
Support for data volumes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 595
- Forks
- 91
- Avg merge
- 9h 35m
- Merged PRs (30d)
- 1
Description
It would be great if there could be an option to attach to the created container a exiting or a new data volume so that databases can be stored in the data volume instead of the container where also SQL Server is running. That would make extremely easy to update SQL Server to a newer version/CU without having to worry about existing databases
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. Begin by locating the CLI path that creates the SQL Server container and reviewing how its container options are represented. Done means users can attach an existing or new data volume so databases persist independently of the SQL Server container.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, databases
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100