How to apply a SQL script
| KB ID: | 1443 |
| Product: | Veeam ONE, Veeam Backup & Replication |
| Version: | All |
| Published: | 2011-12-14 |
| Last Modified: | 2021-06-14 |
Purpose
Instructions to run a SQL script against a MS SQL database.
Solution
To run a SQL script from a command line, perform the following steps:
- Save the script as *.sql file (e.g. script.sql) to local disk
- Make sure that no jobs are running
- Run the following command:
sqlcmd -S <SqlServerName>\<SqlInstanceName> -d <SqlDatabaseName> -i PATHTOSCRIPT\script.sql -o c:\resetresult.txt -I
- Restart the Veeam services
You may also run a SQL script from SQL Server Management Studio, right-click on your database and choose the “New query” option, insert the text from the file, and click Execute.
SQL Server Management Studio can be found here:
https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms
Information about the Veeam Backup & Replication configuration database can be found in the registry under these registry values:
- HKLM\Software\VeeaM\Veeam Backup and Replication\SqlServerName
- HKLM\Software\VeeaM\Veeam Backup and Replication\SqlInstanceName
- HKLM\Software\VeeaM\Veeam Backup and Replication\SqlDatabaseName
If the script needs to be applied to the Backup Enterprise Manager database, please use:
- HKLM\Software\VeeaM\Veeam Backup Reporting\SqlServerName
- HKLM\Software\VeeaM\Veeam Backup Reporting\SqlInstanceName
- HKLM\Software\VeeaM\Veeam Backup Reporting\SqlDatabaseName
| KB ID: | 1443 |
| Product: | Veeam ONE, Veeam Backup & Replication |
| Version: | All |
| Published: | 2011-12-14 |
| Last Modified: | 2021-06-14 |
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
