This guide shows how to restore a .bak file into SQL Server 2022 or SQL Server Express using SQL Server Management Studio (SSMS) only. No T-SQL required.
Prerequisites
• SSMS installed and you can connect as a login with restore rights.
• The .bak file is accessible from the SQL Server machine. If the .bak is on your workstation and the SQL Server is remote, copy the .bak to a folder on the server (for example C:\Backups). Make sure the SQL Server service account has read permission to that folder.
• Know whether you are restoring to a new database name or overwriting an existing one.
Part A: Restore to a new database
1) Open SSMS and connect to your SQL instance.
2) In Object Explorer, right-click Databases -> Restore Database...
3) Source: select Device, click the ... button, then Add, browse to the .bak file, click OK, then ensure the correct backup set is checked.
4) Destination: in Database, type the new database name you want (for example MyApp_Prod).
5) Click the Files page on the left.
6) If you want to control where the .mdf and .ldf will be placed, check Relocate all files to folder and set the Data and Log folders. Otherwise, review the Restore As paths to avoid file name conflicts.
7) Click the Options page on the left and make sure:
• Recovery state is RESTORE WITH RECOVERY (default) so the database comes online after restore.
• Leave Overwrite existing database unchecked since this is a new name.
• Optionally check Close existing connections only if the name already exists and has active connections.
8) Click OK to start the restore. Wait for the success message.
9) Expand Databases and verify your new database appears. Right-click it -> Properties -> Files to confirm the file locations.
10) If the app uses SQL logins, map or create any needed logins under Security -> Logins and ensure database users exist and have proper roles.
Part B: Overwrite an existing database
1) Make sure you are comfortable replacing the current data with the backup contents.
2) In SSMS, right-click the database you will overwrite -> Tasks -> Restore -> Database...
3) Source: select Device, click the ... button, Add the .bak, choose the backup set to restore.
4) Destination: confirm the Database name is the one you are overwriting.
5) Click the Options page:
• Check Overwrite the existing database (WITH REPLACE).
• Check Close existing connections to the destination database.
• Recovery state should be RESTORE WITH RECOVERY unless you plan to apply additional differential or log backups.
6) Click the Files page if you need to adjust file locations or names. Ensure the Restore As paths point to valid data and log folders and do not conflict with other databases.
7) Click OK to restore. After completion, refresh the database node and verify tables, views, and permissions.
Notes on common issues
• Access to the .bak: If you see an access denied or cannot find file error, confirm the .bak is on the server and that the SQL Server service account has read permission.
• File name conflicts: If you restore a backup from a database with different file names, use the Files page to edit the Restore As file names or check Relocate all files to folder.
• Multiple backup sets: If the .bak contains several backups, choose the latest full backup you intend to restore. If you also have differential or log backups, restore them in order and use WITH NORECOVERY until the last one.
• Collation or version differences: You can restore from older to newer SQL Server versions, not vice versa. Collation changes require additional steps after restore.
• Orphaned users: After restore, if a login exists on the instance but the mapped database user is orphaned, fix mapping by creating or mapping the login and updating the user mapping in SSMS (Database -> Security -> Users).
Default data folders (example)
• SQL Server Express 2022 default data path often looks like:
C:\Program Files\Microsoft SQL Server\MSSQL16.SQLEXPRESS\MSSQL\DATA
• Your path may differ based on instance name and install location.
Quick checklist
• .bak copied to server and readable.
• Restore Database wizard launched from SSMS.
• Correct backup set selected.
• Destination name correct.
• Files page reviewed to avoid conflicts.
• Options page set to Recovery: WITH RECOVERY and Overwrite only when intended.
• Restore completed and database visible.