Add SQL Writer log to capture for SQL IaaS #272
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A new log introduced by SQL Server 2019 (15.x) to provide better visibility on its SQLWriter operations. This functionality was also made available in SQL Server 2016 (13.x) Service Pack 3, and SQL Server 2017 (14.x) Cumulative Update (CU) 27.
Azure Backup for VM and Azure Site Recovery use VSS for backups and therefore including this file will help with investigation of these types of cases with the collection of the logs and not needing to ask the customer to provide the data thereby speeding up case resolution.
The file paths are fixed regardless of SQL Server version to:
I believe my wildcard (e.g. copy,/Program Files/Microsoft SQL Server/90/Shared/SqlWriterLogger*.txt) will find either/both of these files if they exist.