Restoring legacy database to SQL Server 2017 using Microsoft SQL Operations Studio

You can restore a database to SQL Server using the SQL Server Management Studio(SSMS). It is a feature rich tool for restoring and backing up databases. Besides restoring and backing up SSMS can carry out a ton of other tasks.

Here is an example of using SSMS to restore a database to SQL Server.

Why use Microsoft SQL Opertions Studio?

For one thing it has small foot print and it is free (preview now). It is lightweight and can do only a few of the things. You can restore a database with fewer clicks than with SSMS.

On my Windows 10 Professional, I have installed SQL Server 2017 Developer edition. I will restore the Northwind database from its backup file on CodePlex. Being a preview, Microsoft SQL Operations Studio has a few kinks and I have a workaround to bypass the kink and get the result.

Watch the video for the restore opeation:
https://www.youtube.com/edit?o=U&video_id=-KOXjlRACSU

Restore operation using Windows PowerShell
https://hodentekmsss.blogspot.com/2016/03/easy-way-to-backup-sql-server-database.html

Read many more related PowerShell posts here.

Installing SQL Server 2017 Developer on Windows 10

This time around it was a plesant surprise. Within a couple of clicks the default instance of SQL Server 2017 Developer is installed!!

Of course you may need to install the various other features later.

Your installation begins here by double clicking the downloaded executable.





Double click the executable. Select the installation type. Of course, the Basic has been chosen here.

 Agree to the License terms by clicking Accept.

 Specify the install location. Here the default is accepted.

 Downloading of installation package beings. This will take some time which depends on your connection to Internet besides others.

 Still downloading the package....

Voila!  It is installed.

You could look at a few things on the above screen. I tried to connect by clicking Connect Now at the bottom and here is a response from SQLCMD.

However when I clicked the SQL Server Install Log folder, the screen froze and I had to reboot. The last part is my experience and yours may be different. Perhaps it does not work well with Build 17025.rs_prerelease Insider Preview version of Windows.

Here is the default installation in SSMS 2017 object explorer: