microsoft / microsoft/sql-server-samples
Data and Log Files for AdventureWorksLT2017 were not renamed
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 11.2k
- Forks
- 9.1k
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 14
Description
If someone tries to restore all 4 AdventureWorksLT[201Y] databases they can restore the 'AdventureWorksLT2012' successfully; however, after that when they try to restore AdventureWorksLT2014.bak, AdventureWorksLT2016.bak, or AdventureWorksLT2017.bak they will receive an error stating "The file '/.../AdventureWorksLT2012_log.ldf' cannot be overwritten. It is being used by database 'AdventureWorksLT2012'
Please rename the data & logfile to be the same year as the database itself, backup the databases, and post the new .bak files when this is complete. This file naming pattern is already being done with the regular AdventureWorks[201Y] databases, as well as the AdventureWorksDW[201Y] 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
Start by inspecting the AdventureWorksLT2012, AdventureWorksLT2014.bak, AdventureWorksLT2016.bak, and AdventureWorksLT2017.bak artifacts and their embedded data and log filenames. Regenerate the backups so each file uses its database year, then verify that all four databases restore without attempting to overwrite another database's log file.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- sql
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100