How to Export SQL Logs
| KB ID: | 2125 |
| Product: | Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0, Veeam Backup & Replication 7.0 |
| Published: | 2016-04-13 |
| Last Modified: | 2021-05-11 |
| Languages: | ES |
Objective
This article documents how to export logs from Microsoft SQL Server using SQL Server Management Studio (SSMS).
Steps
The following steps require Microsoft SQL Server Management Studio (SSMS).
1. Open Microsoft SQL Server Management Studio and connect to the SQL Instance for which SQL Server Logs are need.
2. Once connected expand the [Management] ➔ [SQL Server Logs] and double-click on the entry named Current
3. Within the Log File Viewer select "Current" and any "Archive" entries which cover the dates that logs are needed for.
4. Then click [Export] to save the logs to a file.
Note: All three file type options for Exporting generate the same file content with a different extension (i.e. log, csv, or txt).
More information
For documentation on exporting logs from Veeam Backup & Replication please review: https://www.veeam.com/kb1832
For documentation on exporting Windows Event Logs please review: https://www.veeam.com/kb1873
For documentation on exporting Windows Event Logs please review: https://www.veeam.com/kb1873
| KB ID: | 2125 |
| Product: | Veeam Backup & Replication 11, Veeam Backup & Replication 10a, Veeam Backup & Replication 9.5, Veeam Backup & Replication 9.0, Veeam Backup & Replication 8.0, Veeam Backup & Replication 7.0 |
| Published: | 2016-04-13 |
| Last Modified: | 2021-05-11 |
| Languages: | ES |
Couldn't find what you were looking for?
Below you can submit an idea for a new knowledge base article.
Report a typo on this page:
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!
Spelling error in text
Knowledge base content request
