All posts tagged sql server 2012

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

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.

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.

The System Configuration Checker will run a discovery operation on your computer. To continue, Click OK. .

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.

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.

The Ready to Remove Node page displays a tree view of options that were specified during Setup. To continue, click Remove.

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.

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

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

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. Provide product key for your media. Then Next

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

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

7. click SQL Server Feature Installation and click Next.

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

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

10. Provide Network and Instance names. Then Next

11. Click Next

12. Click Next

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

14. Enable IP4 and provide IP address. Then Next

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

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:

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.

Right click on setup and Click Run as administrator

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

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

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).

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

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

Enter the product key and click Next

Read and accept the licence Terms to proceed.

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.

Select the features to install and click Next

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

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.

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

Select the accounts to run SQL Services and Click Next.

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

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.

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.

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.

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.

you can change the file locations if you want.

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.

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.

Specify controller name and click Next.

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

Click on Install button to start Installation.

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

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

Follow Blog via Email

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 2 other followers

Disclaimer

This is a personal weblog. The opinions expressed here are my own and not of my employer. For accuracy and official references refer to MSDN, Microsoft TechNet, Books Online. I or my employer do not endorse any of the tools / applications / books / concepts mentioned here on my blog. I have simply documented my personal experiences on this blog.