SQL Server Setup Installation taking very long time

I had to install  a standalone instance of SQL Server 2012 [developers edition] on one of the machine. Usually the whole installation finishes within an hour or two.  I started the installation process after passing all the required parameters and switched to another work [multitasking 😉 ].  It wasn’t a high priority task, so I went for lunch also. When I came back, it was almost 2 hours since the setup installation was running. To my surprise it was still running [Status bar was showing it stuck at around 30% It was stuck at Install_SqlSupport_KatmaiRTM_Cpu64_Action:CreateShortcuts. Creating shortcut].  I went through the sql server setup logs to check if there is something useful pointing to the reason behind SQL Server taking forever to finish.  I checked event logs as well but to no avail.

 

 

I started my hunt for a solution to this problem on internet .

I am sharing the trick that solved the issue for me:  🙂

 

I cancelled the currently running installation setup.

Followed the below steps.

  • Open Internet Explorer
  • Go to Setting -> Internet Options
  • Open the “Advanced” Tab
  • Go to security sections below and uncheck the “Check for server certificate revocation” and “check for publisher certificate revocation options”
  • Click Apply and then OK
  • Close the browser and reboot the system.

After this when I re-initiated the Installation. It finished in normal time. 🙂

 

 

Hope it was helpful !!!!!

 

 

SQL Server- Installing SQL Server 2014

In this tutorial, I will show you step by step installation of SQL Server 2014 Evolution version (Default Instance).

Before you start, it’s highly recommended to check hardware and software requirements for Installing SQL Server 2014.

 

Step By Step (Installation)

1. Go to the Installation Setup (SQL Server 2014). Right click setup.exe and run as administrator.

1

2. Upon starting the installation, you will get this window. Go to the Installation tab on the left and then click “New SQL Server stand-alone installation or add features to an existing installation.

 

2

3. Enter the product key and click Next

 

 

3

4. Accept the license term in order to continue.

 

 

4

5. It checks your machine to make sure it meets the hardware and software requirements to install SQL Server. If you get any Errors in the results, do not move to the next step.

 

 

5

6. Choose the first option in order to install SQL Server, and Click Next.

 

6

7. Select which features to install. I have selected only limited features (Database engine, management tolls, client tools, integration services). Click Next to continue:

 

7

8. Select Default instance and click next.

 

 

8

9. In this step you can select the service accounts for the SQL Server actions. Each service in SQL Server represents a process or a set of processes to manage authentication of SQL Server operations with Windows. Each service can be configured to use its own service account. Its recommended to use domain account to run sql services in production. However, i have slected local account.  Click next to proceed.

 

9

10. Select collation and click next.

 

 

10

11. SQL Server can operate in one of two security (authentication) modes: (a) Windows Authentication mode which allowed a user to connect through an operating system user account. or (b) Mixed Mode which allowed users to connect to an instance of SQL Server using either Windows Authentication or SQL Server Authentication.

I have selected Mixed Mode and have spacified password for sa account.  I have also added my account as sql server adminstrator. Click next to proceed.

 

 

11

12. By default SQL Server uses the system operation disk  Thus it is highly recommended to use the best practice according to your specific system and usage. Separating the LOG files from the data files can improve performance significantly. The system database tempDB is used extensively by SQL Server. This database is rebuilt each time the server is restarted. It is best practice to separate data, transaction logs, and tempdb for environments where you can guarantee that separation.

As i have installing SQL on a virtual machine which has only one drive i.e C. I am going ahead with the default directory locations. Click next to proceed.

 

 

 

12

13. Review the summary of features and components for your SQL Server installation. To proceed, click Install

 

13 14 15 16

14. On the “Complete” page, you can view the Setup summary log by clicking the blue link provided on the bootom this page. To exit the SQL Server Installation Wizard, click Close. We have successfully installted SQL Server 2014.

 

 

 

17

Connecting to SQL Instance:

Go to the Start menu, and choose SQL Server 2014 Management Studio (SSMS), to connect to the newly created instance of SQL Server 2014

 

 

18

 

 

 

Hope this was helpful !!!

SQL Server – Uninstall /Remove SQL Server 2012 Failover Cluster Instance

Procedure to uninstall a SQL Server failover clustered instance

To update or remove a SQL Server failover cluster, you must be a local administrator with permission to login as a service on all nodes of the failover cluster.

 

To remove a node from an existing SQL Server failover cluster

  1. Insert the SQL Server installation media. From the root folder, double-click setup.exe. To install from a network share, navigate to the root folder on the share, and then double-click Setup.exe.
  2. The Installation Wizard launches the SQL Server Installation Center. To remove a node to an existing failover cluster instance, click Maintenance in the left-hand pane, and then select Remove node from a SQL Server failover cluster.
  3. The System Configuration Checker will run a discovery operation on your computer. To continue, Click OK. .
  4. After you click install on the Setup Support Files page, the System Configuration Checker verifies the system state of your computer before Setup continues. After the check is complete, click Next to continue.
  5. On the Cluster Node Configuration page, use the drop-down box to specify the name of the SQL Server failover cluster instance to be modified during this Setup operation. The node to be removed is listed in the Name of this node field.
  6. The Ready to Remove Node page displays a tree view of options that were specified during Setup. To continue, click Remove.
  7. During the remove operation, the Remove Node Progress page provides status.
  8. The Complete page provides a link to the summary log file for the remove node operation and other important notes. To complete the SQL Server remove node, click Close.

 

Screenshots: 

1 2 3 4 5 6 7

 

 

Repeat above steps on all nodes used for the SQL Server clustered instance. Make sure you uninstall the active node last.

Note:    Remove Passive Nodes First and Active node Last.

SQL Server – Error while enabling Windows feature: NetFx3

Problem:

I was installing SQL Server 2012 on Windows Server 2012, and the installation failed with the following error.

 

Error while enabling Windows feature: NetFx3, Error Code: -2146498298, Please try enabling
Windows feature: NetFx3 from Windows management tools and then run setup again. For more
information on how to enable Windows features, see http://go.microsoft.com/fwlink/?linkid=227143

1

 

Reason:

Since I didn’t enable .NET Framework 3.5 before installing SQL Server 2012 it failed.

 

Solution:

Enable .NET Framework 3.5 and then install SQL Server 2012.

Below is the procedure to enable .NET Framework 3.5 in Windows Server 2012

 

Using GUI

1. Go to Server Manager -> Manage -> Add Roles and Features

2

2. Click Next

 

3

3. Click Next button, the wizard will shows the Installation Type section where we have to select the Role-based or feature-based installation option that it has used to configure this server by adding roles, role services and features.

 

 

 

4

4. Click Next button, it will show the Server Selection section. Click Select a server from the server pool and over the grid, select the server

 

 

5

5. Click Next

 

6

6. Select the .NET Framework 3.5 Feature Checkbox and click Next.

 

7

7. Warning message informs us that for one or more installation selections are missing source files on the destination server, so we have to specify an alternative source path. Click the Specify an alternative source patch

 

 

8

8. Provide the required source file path for the .Net Framework 3.5 which is in Windows Server 2012 ISO file. Extract or Mount this. and click OK

 

9

9. TheResults section will show the installation status. Installtion will complete.

 

10

 

Once .net framework 3.5 is enabled. We can install SQL Server 2012 on Windows Server 2012.

 

 

Using Command Line

dism /online /enable-feature /featurename:NetFx3 /source:d:\sources\sxs

11

 

 

 

Hope this was helpful !!!

 

SQL Server – Adding Node to SQL Server 2012 cluster

Adding Node to SQL Server 2012 cluster

This is part 2 of earlier post. Installing SQL Server 2012 Cluster

https://exploresqlserver.wordpress.com/2014/11/11/sql-server-installing-sql-server-2012-cluster/

 

 

1. Run setup.exe and Click the Add node to a SQL Server failover cluster link

2

2.  Install Support rules and Make Sure all passes.  Few steps are similar to Node 1 Installation

 

23

3. Make sure nothing has failed in Setup Support Rules. Then Click Next.

 

4

4. Enter the product Key and click Next

 

5

5. Accept License Terms and click Next.

 

 

6

6.You will see that setup has detected the current Single node cluster from above, click Next

 

7

 

8

7. Enter Service account credentials and click NEXT.

 

9

8. Click Next

 

 

10

9. Make sure nothing had failed in Add Node Rules check. Then click Next.

 

 

11

10. click Install.

 

 

 

12 13

11. In the Complete dialog box, click Close. This concludes installing the passive node of a SQL Server 2012 Failover Cluster

 

 

 

14

 

 

 

SQL Server – Installing SQL Server 2012 Cluster

Microsoft Cluster

A Microsoft cluster is a high-availability system designed to keep the database up as much as possible. It does this by resuming processing on the secondary server in the event of a failure on the principal server. Since the data resides on a shared disk, a Microsoft cluster will not survive a data corruption.  This technology is high availability, not disaster recovery. All data resides in the same data center and on the same disk. A cluster can be used with other technologies, such as database mirroring.

 

architechture

 

 

In order to Install SQL Server Cluster, we need to have Windows cluster ready as a base with some other pre-requisites as well. [ Installing Windows Cluster is out of scope of this article.]

1- Windows Cluster

2- DTC

3- SQL

 

prerequisites

 

We then need to setup 2 Network Interfaces to be used in production and the other as a heartbeat.

Once the setup is ready to install SQL Server Cluster. Please follow the below steps to configure 2 Node Active/Passive Cluster[SQL Server 2012].

Installation:

Steps to be performed on Node 1.

1. With the SQL Server installation binaries available, right click “Setup” and run as administrator:

1

 

2

 

2.  Click “Installation” in the left menu, then select “New SQL Server Failover Cluster Installation”

 

3

 

3. A check will run in order to find possible constraints when installing the SQL Server Setup support files. At the end of the check, click “OK”

 

4

 

4. Provide product key for your media. Then Next

5

 

5. Accept License Agreement (and the other check if you would like). Then Next

6

6.  Wait for Setup Support Rules check. Once done make sure no failed task. Evaluate warnings for your environment . Then click Next

 

7

 

7. click SQL Server Feature Installation and click Next.

8

 

8. Select Features to install and click NEXT. I have selected all Features.

9

9. Make sure feature Rule check complete with no Failed status. Then Next

 

 

 

10

10. Provide Network and Instance names. Then Next

 

 

 

11

11. Click Next

 

12

12. Click Next

 

 

13

13. Select Disk needed for the resource group . Then Click Next

 

14

14.  Enable IP4 and provide IP address. Then Next

 

15

 

15. Provide Service Accounts (and Collation if different than default – SQL_Latin1_General_CP1_Cl_AS). Then Next

16 17

16. Now we need to choose the authentication mode of our instance.The options are either “Windows Authentication”, which will take benefit from domain and local server logins, or “Mixed Mode”, which accepts Domain/Windows logins as well as logins created and managed by SQL Server.If you pick “Mixed Mode” a login called “sa”, member of the “Sysadmin” role will be enabled. For this reason we need to specify the password for this login.In the box bellow, we need to add all domain/Windows users that have access to the instance and will be part of the “Sysadmin” fixed server role. You need to use the three buttons to add/remove logins from this list:

 

18

17. Select data directories accordingly for Datafile, log file, tempdb files and backup files and click next.

 

19

18. If you have selected analysis features then on this screen add the administrator account and data directory for analysis service. Then click next

 

20

 

 

21

 

19. Select install only for reporting services and Click Next. You can configure reporting services later.

 

 

 

22

20. Check the error report and click NEXT.

 

 

23

21. Make sure no clusters rules failed. Then Next

 

24

22. Click Install.

 

25 26

 

29

23. Click Close to complete the installation.

 

 

30

 

Check the Failover Cluster Manger. And you would see SQL Service and other dependent resources running under it.

 

31

 

 

Adding Node to cluster will be covered in next post.

https://exploresqlserver.wordpress.com/2014/11/11/sql-server-adding-node-to-sql-server-2012-cluster/

 

 Hope this was helpful !!!

 

Installing SQL Server 2008 R2 Cluster

https://exploresqlserver.wordpress.com/2014/08/17/installing-sql-server-2008-r2-cluster/

 

 

SQL Server – How to configure MSDTC in Windows Server 2012 Cluster

Below are the steps to configure MSDTC in Windows Server 2012 Cluster:

1. Open Failover Cluster Manager and Right-click on Roles and pick the “Configure Role” option.

1

2. Choose the option “Distributed Transaction Coordinator (DTC)” from the list. Click  “Next”.

2

 

3. Provide Name and IP for new role selected (Distributed Transaction Coordinator)

3

 

4. Select the Disk to be used for MSDTC

4

 

5. Review the configuration and confirm by clicking next.

5

 

6. The installation will run and in the last step you will show summary report. Click “Finish”.

6

 

7. Now you will be able to see a DTC role in the Failover Cluster Manager.

7

 

 

Hope this was helpful !!!

 

Installing SQL Server 2012

This post will serve as a step by step guide to install SQL Server 2012.   Once you are ready with the OS setup and good to go for SQL Server 2012 Installation follow the below steps.

 

Copy the sql server 2012 setup onto the machine where you want to install it.

1

 

Right click on setup and Click Run as administrator
2

Go to Installation page and click on New SQL Server stand-alone installation

 

3

 

Setup Support Rules screen check whether all prerequisites are in place.

4

Click on show details to confirm all rules have passed and proceed by clicking OK. (if there are any failures then exit setup by clicking cancel and resolve the issue before running the setup again).

 

5

 

Setup Support Rules screen check whether all prerequisites are in place.  Click Next to proceed.

 

6

In my case, I already have a named instance installed on my machine. That is why add features to an existing instance of SQL 2012 is enabled.

however, ignore this and select Perform a new installation of SQL Server 2012 and click Next

7

Enter the product key and click Next

8

 

Read and accept the licence Terms to proceed.

9

Here you have two option for installation. first is custom installation, which means you can pick and choose the features you want to install.

Second is to install all Features with Default settings. It is always recommended to install only those features which are required.

10

Select the features to install and click Next

11

Setup will run some rules to foresee any issue. Click Next once complete.

12

Here you have two options to select the type of instance.

Default instance or Named Instance. You can install only only one default instance but can install multiple named instances.

 

13

Review the disk space summary. It will not allow you to proceed if you don’t have enough disk space.

14

 

Select the accounts to run SQL Services and Click Next.

15

You can change the collation if you want. Better leave it default and click Next.

16

 

Choose the authentication mode. Recommended mode is Windows Authentication, as it is more secure. However, if business require select mixed mode. Enter Sysadmin (sa) password twice and select SQL Server admins for this instance and click Next.

 

 

17

Select the Data Directory. If you want you can change it to some other drive. I have left it default.

As per best practices, Data, log, tempdb and backup files should all be on separate drives.

18

FILESTREAM enables SQL Server-based applications to store unstructured data, such as documents and images, on the file system. If required, select this feature, else click Next to proceed.

19

 

If you have selected Analysis Services in Feature Selection page then you will get this.  Specify Users to have Administrative permissions and click on Data Directories tab.

20

you can change the file locations if you want.

 

21

You will get this screen, if you have selected Reporting Services in Feature Selection Page. You have two options here, first to install and configure Reporting Service or Install only.

22

Distributed Replay feature helps you assess the impact of future SQL Server upgrades. Similar to SQL Server Profiler, you can use Distributed Replay to replay a captured trace against an upgraded test environment. Unlike SQL Server Profiler, Distributed Replay is not limited to replaying the workload from a single computer.

Specify users who will have permissions for Distributed Replay controller service.  Group accounts are not support. If you enter group account, it will throw validation error as below.

23

 

24

Specify controller name and click Next.

25

If you want to send windows and SQL Server Error reports to MS then click on check box and click Next.

26

 

27

Click on Install button to start Installation.

28

 

29

After a successful installation, the screen should be all green (as below).

30

Now you have successfully installed SQL Server 2012. Open the management studio to check.

 

 

31

 

I hope this article was helpful.

 

Applying service packs (Hotfixes) to SQL Server Cluster 2008R2

When an instance of SQL Server is configured for HA like Cluster, then it is important to install service packs (hot fixes) in proper sequence.

Installing Service Pack SQL Server 2008/R2 in failover cluster is very different than the SQL Server 2005 cluster failover.

With SQL Server 2005,  install service pack (or hotfix) on the active node and the Setup will launch simultaneously  “remote silence” on all passive nodes. All nodes in the cluster containing the SQL Server instance are updated in the same time.

With SQL Server 2008, to reduce the downtime, the method of deployment is changed.

Below is the sequence to apply Service Pack, Cumulative Update or Hotfix in SQL Server 2008/R2 Cluster (2 Node Active/Passive :

1.  Apply the hotfix on pasive node (Node 2)
2.  Reboot the passive node (Node 2)
3.  Failover SQL resources from Node 1 to Node 2. This will make Node 2 Active and Node 1 Passive.
4.  Apply the hotfix on now passive node (i.e Node 1)
5.  Reboot the passive node Node 1.

 

Below are the screenshots for reference:

Download the Service Pack 1 and run the .exe (Node 2– Passive Node)

1

Click Next to Proceed

 

9

 

 

Accept licence terms and click Next

10

Make sure the SQL instance which needs to the patched is selected and click Next

11

Click Next, once files in Use completes.

12

 

Click Update to upgrade Service pack.

 

13

 

14

Once finished, Click close.

15

 

This complete the step 1.  Now reboot the currently patched node and then failover SQL resources to Node 2 from Node 1.

Repeat the same process of applying patch, on Node 1 now.  Once finished, take reboot of Node1 and check the status.

This completes the task of applying Service pack on SQL Cluster 2008/R2.

 

Hope this was helpful.

Installing SQL Server 2008 R2 Cluster

Microsoft Cluster

A Microsoft cluster is a high-availability system designed to keep the database up as much as possible. It does this by resuming processing on the secondary server in the event of a failure on the principal server. Since the data resides on a shared disk, a Microsoft cluster will not survive a data corruption.  This technology is high availability, not disaster recovery. All data resides in the same data center and on the same disk. A cluster can be used with other technologies, such as database mirroring.

Below is the SQL Cluster Architechture:

Architechture

 

 

 

In order to Install SQL Server Cluster, we need to have Windows cluster ready as a base with some other pre-requisites as well. [ Installing Windows Cluster is out of scope of this article.]

1- Windows Cluster

2- DTC

3- SQL

Below IPs needs to be reserved well in advance to save yourself some time. IP Addresses and Hostnames can be of your choice.

Prerequisites

 

We then need to setup 2 Network Interfaces to be used in production and the other as a heartbeat.

Once the setup is ready to install SQL Server Cluster. Please follow the below steps to configure 2 Node Active/Passive Cluster[SQL Server 2008 R2].

 

Installation:

Steps to be performed on Node 1.

  1. Run setup.exe from the installation media to launch SQL Server Installation Center. Click on the Installationlink on the left-hand side1
  2. Click the New SQL Server failover cluster installation link. This will run the SQL Server 2008 R2 Setup wizard2

 

3. In the Setup Support Rules dialog box, validate that the checks return successful results and click Next.

3

4. In the Product Key dialog box, enter the product key and click Next.

4

5. In the License Terms dialog box, click the I accept the license terms check box and click Next.

5

6. In the Setup Support Rules dialog box, click Install. Validate that the checks return successful results. If the checks returned a few warnings, make sure you fix them before proceeding with the installation.

8

7. Select the features to install and click Next.

9

 

8. Configure the Network Name ( this is going to be the DB cluster name ) and instances

10

 

9. In the Disk Space Requirements dialog box, check that you have enough space on your local disks to install the SQL Server binaries and click Next.

11

10. Choose your Cluster Resource Group ( or leave to default )

12

 

11. In the Cluster Disk Selection dialog box, select the available disk groups that are on the cluster for SQL Server to use.

13

 

12. In the Cluster Network Configuration dialog box, enter the IP address and subnet mask.

14

 

13. In the Cluster Security Policy dialog box, accept the default value of Use service SIDs (recommended).

15

14. In the Server Configuration dialog box, enter the credentials that you will use for your SQL Server service accounts in the Service Accounts tab. Configure the Service accounts Users and Password as per best practices.

16

 

15.  Select the appropriate Authentication Mode. If you want to add the currently logged on user to be a part of the SQL Server administrators group, click the Add Current User button.

17

16. On the Data Directories tab, enter the path where your system and user database files will be created.

18

17. Install, But do not configure is the only option available as we haven’t installed the pre-requisites for Reporting Service.

19

 

18. Make Sure everything passes on the Cluster installation Rules

21

 

19. Review your install Summary and Click Install

22

 

20. Now wait for the installation to finish

23

 

21. In the Complete dialog box, click Close. Cluster Installation on Node 1 is finished.

24

 

 

Now, start installation on Node 2.

1. Run setup.exe and Click the Add node to a SQL Server failover cluster link

25

2.  Install Support rules and Make Sure all passes.  Few steps are similar to Node 1 Installation

26

27

28

 

30

 

 

31

 

3. You will see that setup has detected the current Single node cluster from above, click Next

 

32

 

4. Enter the same credentials and click Next.

 

33

 

5. Make sure everything is green.

 

 

35

 

6. In the Ready to Update dialog box, verify that all configurations are correct and click Install.

 

36

 

7. In the Complete dialog box, click Close. This concludes installing the passive node of a SQL Server 2008 R2 Failover Cluster

 

39

 

Verifying The Cluster

 

FailoverCluster

 

 

Hope this was helpful.