Non-Production Database Stuck in a Restoring State

Non-Production database has been stuck in a restoring state since trying to run a refresh

• Munis
• EERP
• Refresh
• Database
• Restoring

Refresh of the Non-Production database from Production failed or the command window was closed before the refresh completed

Perform the following for the database stuck in a restoring state.

1. Open SQL Server Management Studio and connect to applicable instance
2. Make note of the database name
3. Make note of database owner
   1. Typically formatted as muntest
   2. This can be obtained from Tyler Deploy under Site Report
   3. If available, you can also right click an alternative non-prod environment and select Properties to see what its database owner is
4. Right click the restoring database and select Delete
   1. A database deletion window will pop up. Select the two checkboxes at the bottom of the general tab:
      1. Close existing connections
      2. Delete backup and restore history for database
5. Click OK
6. Once complete, on the SQL server, navigate to the MSSQL\DATA folder
   1. Ex: <DRV>:\mssqldata\MSSQL15.MSSQLSERVER\MSSQL\DATA
   2. Or <DRV>:\mssqldata\MSSQL15.TYLERCI\MSSQL\DATA
7. Delete any remaining database files for that environment
   1. Ex. muntest.mdf and muntest_log.ldf
8. Recreate the database
   1. Right click on Databases and select New Database
   2. Enter Database Name and Owner (example: Database name: muntest; Owner: muntest)
9. Run refresh script for the environment

• Manual Refresh of Munis database through SSMS
• How to manually refresh AWS EERP environments