SaaS: Please contact TSM Support for assistance On-Prem: From the database server, launch and sign into Back Up Database(s) Log into the source environment's database server with tylerservice or an administrative account Open Microsoft SQL Server Management Studio (SSMS) with and connect to the specific server nameFrom the Object Explorer (on the left), ensure the server's drop down has been selected, right click Databases, click Restore DatabasesFrom the Restore Database window, under Source click the button for Device and click the button labeled ... to the right Click Add to see a list of .bak database backups within the default backup folder or browse to a specific folder as neededClick the database (IE: <database.bak>) to be restored- Verify the Destination database is correct
Click the Options tab on left of the Restore Database windowCheck the name for the instance where the source database resides Expand Databases Right click the database name and select Tasks > Back Up... Back up to Disk If there is a location already populated, remove it and click Add... to choose the desired file name and location Note: You need to add the .bak file extension to the end of the file name (Ex: D:\TylerTempBackups\munprod_01012023.bak)
Click the Media Options tab Select Overwrite all existing backup sets Click OK when you are ready to start the backup and let the backup run until completion If the destination database is hosted on a different server, place a copy of the backup file on the destination database server Back up destination database (optional)
Restore Destination Database Connect to the SQL instance where the destination database resides Expand Databases Right click the destination database and select > Tasks > Restore > Database... Click the Options tab Under Restore Options, check off Overwrite the existing database (WITH REPLACE)
restore optionCheck the Close Existing Connections option - If these are grayed-out, close and re-open the restore window and choose them before selecting the device to restore fromIf the destination database name is different from the source, select the destination. Otherwise, click OkRight click on the server name under Object Explorer and click RefreshThe newly restored database should populate under the Databases dropdownRight-Click the newly restored Database and click PropertiesClick on the Files tab and verify or change the filenames to the appropriate environment (IE if munprod was restored to muntrain, the .mdf and .ldf filenames in this tab need to be renamed to reflect the correct environment)On the Files tab, set the owner to satylerClick the Options tab and select the latest version available in the Compatibility Level drop down menuUnder Server connections, check off Close existing connections to destination database Note: If you select your source before going to the Options tab, Close existing connections to the destination database may not be available to select.
Click the General tab Under Source, select Database or Device radio option Device (with the backup path populated) will be the typical selection
Database - Select the database to restore from the drop-down list. The list contains only databases that have been backed up according to the MSDB backup history. Device - Select a specific backup file to backup from. This is the typical selection. Click the ellipses Click Add Locate backup file and click OK Click OK
Under Destination, select the database to be restored
Click the Files tab Expand the Restore As column and verify that this row matches the location of your target MDF and LDF Click OK when you are ready to start the restore. Let run until completed.
If the source environment is different than destination environment, Once the restore completes, right click destination database name and select New Query Run the query below to change the database owner. Update database name and owner as needed. USE muntest EXEC sp_changedbowner 'muntest'
Right click the newly restored database and click Properties Click the Files tab Verify Owner is set correctly (Ex: cashtest) Under Database files, update Logical Name if needed (Ex: muntest and muntest_log) Click OK
Redeploy product environment from Tyler Deploy with Force Redeploy checked off
|