SQL Server 2014 Installation Steps

Step 8 - In Setup Role: Select SQl Server Feature Installation and click on Next,

Step 9 - In Feature Selection: Select features as All, Instance Saving location can be changed and click Next,

Step 10 - In Instance Configuration: You can select Default option for default instance name, my system already has server instances, so I selected Named instance for new instance name, Now click on Next.

Step 11 - In Server Configuration: Click on Next.

Step 12 - In Database Engine Configuration: You have the option to provide Window authentication or Mixed Mode for separate login accounts. Make Sql Server Login account and click on Add Current User to add windows authentication for existing user. Click on Next.

Step 13 - In Analysis Services Configuration: Click on Add Current User for login authentication and click on Next.

Step 14 - In Reporting Services Configuration: Select Install and Configure option and click Next.

Step 15 - In Ready to Install: Provide Configuration files saving path on your system. Click Install.

Step 16 - Now you will see Installation Progress as in the following,

Step 17 - Once Installation is completed, you will see Features as Succeeded. Now click Close.

Now search SQL Server 2014 Management Studio in your system search/window 10 cortana by typing …SQL. Here's the screenshot,

Example

Click on SQL Server 2014 Management Studio

Then select Server name: It is the server instance you have created or if you have multiple instances just click on Browse for more and select the desired server.

When you clicked on Browse for more, the following window will open, select your server name instance that you have created in it.

Once login is done you can access SQL Server that you have created: MSSQLSERVER2 is the one I have installed and it is ready for use as in the following,

Here's a free e-book on SQL Server: Introducing Microsoft SQL Server 2014

Diagnosing deadlocks in SQL Server with Extended Events

Error 1205 again? Pull the deadlock graph from the system_health session, read it like a DBA and fix the access pattern that causes it.

#concurrency#locking#troubleshooting