Select SQLSERVERUA2 from the list box as the instance of SQL Server to remove features from. See Figure 2-53

3. In the Programs and Features window, scroll down the list of installed programs, and double-click Microsoft SQL Server 2012 (64-bit). Click the Remove link from the SQL Server 2012 dialog box to launch SQL Server 2012 Setup. See Figure 2-52.

Figure 2-52 Uninstall or change a program window

Microsoft Windows Server 2008 R2

Figure 2-53 Remove SQL Server 2012–Select Instance window

Microsoft SQL Server 2012

2

7. In the Removal Rules window, verify that all tests have passed. Review any warnings, and follow the instructions given to correct any failures before proceeding to the next step. Click Next.

8. In the Ready to Remove window, review the features to be uninstalled, and then click Remove. See Figure 2-55.

9. During uninstall, a blue progress scroll bar provides you with the status of the repair.

Wait for the uninstall operation to complete. This will take less than a minute.

10. Once the uninstall operation is complete, a window displays the status. You can review a detailed log of the repair operation by clicking the link to the Summary log file in the lower pane of the window. Click Close. See Figure 2-56. You should now review the steps outlined in Activities 2-2 and 2-3 to validate your install and check the system changes.

6. Click Next. In the Select Features window, click Database Engine Services to select it, and then click Next. See Figure 2-54. Unless you are undertaking a complete unin-stall, do not select any Shared Features because this will remove those features for all other instances of SQL Server 2012 on the server.

Figure 2-54 Remove SQL Server 2012–Select Features window

Microsoft SQL Server 2012

Figure 2-55 Remove SQL Server 2012–Ready to Remove window

Microsoft SQL Server 2012

Figure 2-56 Remove SQL Server 2012–Complete window

Microsoft SQL Server 2012

2

Chapter Summary

• The planning stage of a SQL Server 2012 installation consists of a set of interdependent activities that include requirements analysis, selection of the edition and license model, feature selection, and hardware and software architecture design. All of these activities are driven by business requirements.

• Physical and logical security should be factored into each stage of the planning process.

Physical security considerations should be addressed by placing hardware in a secure location with physical access controls. Logical security considerations should include minimizing the security footprint of the installation, isolating the services using individual service accounts, and installing SQL Server on a dedicated server.

• Up to 50 instances of SQL Server 2012 can be installed and run concurrently on the same host. Each instance has a set of features that is unique to that instance (e.g., Database Engine, Analysis Services, Integration Services, and Reporting Services), while other features are shared (e.g., management tools).

• The SQL Server Features Discovery Report can be run to list the installed instances, features, and shared features on the server.

• SQL Server 2012 can be installed using the installation wizard or the command prompt in attended mode. The command prompt and SysPrep can also be used for installing an in-stance or features in unattended mode.

• Changes to the server should be validated after an installation using Windows management tools such as the Registry Editor, Performance Monitor, Resource Monitor, and SQL Server Configuration Manager.

• Corrupt or missing application files and Registry settings, or bad configuration parameter values, may cause a SQL Server 2012 instance to fail to start. A repair operation can be run from the SQL Server Installation Center to replace corrupt or missing files and bad settings with their defaults.

• An uninstall operation should always use the functionality provided by the Uninstall or Change a Program feature that can be accessed from the Windows Server 2008 R2 Control Panel.

• Always take a full backup of all databases before making any changes in a production environment—for example, when adding or removing features.

Key Terms

AlwaysOn   A high-availability and disaster recovery solution offered in the Enterprise Edition of SQL Server 2012; requires additional servers and storage devices that are connected over a network.

Analysis Services   A data mining and analytical component of SQL Server 2012.

attended installation   An interactive installation of SQL Server 2012 completed using either the installation wizard or the command prompt.

Availability Groups (AG)   A compononent of AlwaysOn functionality; consists of a group of primary user databases with up to four replicas that will be used in the event the primary user database fails.

collation   A database setting that specifies the character set, sort order behavior, and how characters are evaluated in comparison operations.

command prompt   A command-line interpreter that provides a means of installing SQL Server 2012—by running setup.exe—and specifying SQL Server parameters on the command line, or by referencing a Configuration File (ConfigurationFile.ini).

default instance   The instance of SQL Server 2012 to which a client who connects to the database will connect to if they don’t specify a named instance; each database server may have

Failover Cluster Instance (FCI)   A set of redundant nodes that can be used to host the database instance should an error occur on the primary node; provides redundancy in the event of hardware or software failure on a SQL Server node.

installation wizard   A Windows application that provides step-by-step guidance though the installation process; launched through the SQL Server Installation Center.

Integration Services   A SQL Server 2012 component that provides extract, transform, and load (ETL) capabilities.

Master Data Services   A SQL Server 2012 component that provides a centralized means to manage and validate data.

named instance   A database instance on a server other than the default instance; each server can support up to 50 instances of SQL Server 2012.

Performance Monitor   A Windows management utility (perfmon.exe) that provides a view of different performance attributes on the host server by viewing data in real time or by replaying data from a log.

Registry Editor   A Windows management utility (regedit.exe) that allows you to view, alter, or delete Registry keys.

Registry key   A configuration value associated with a particular Windows software application.

Reporting Services   A set of tools and services in SQL Server 2012 that enable you to create, deploy, and manage reports.

Resource Monitor   A Windows management utility (resmon.exe) for monitoring hardware resource utilization in real time using five individual tabs: Overview, CPU, Memory, Disk, and Network.

shared features   A set of SQL Server features that are shared between multiple instances of SQL Server 2012 on a single host; includes many of the management tools, Integration Services, and Master Data Services.

SQL Server Configuration Manager   A tool for configuring SQL Server 2012 network protocols and managing component services.

SQL Server Features Discovery Report   A report that displays the SQL Server 2012 instances, tools, and features currently installed on the server.

SQL Server Installation Center   A user interface that provides a single point of access to the various planning, installation, and maintenance wizards.

SQL Server parameters   Settings entered during the SQL Server 2012 installation process; used to specify the type of setup (install, uninstall, or upgrade), features to install, and other configuration settings. SQL Server parameters are specified manually for a command-line install or are generated automatically by the installation wizard to a ConfigurationFile.ini file.

system database   A database created during the SQL Server installation process for storing system configuration information.

unattended installation   A noninteractive installation of SQL Server 2012 completed either by using the command prompt combined with a configuration file and the quiet parameter or by using the SysPrep utility to create an image file for virtual deployments.

user database   A database that contains the data associated with a client application; each SQL Server instance may have one or more user databases.

virtual account   An auto-managed local service account, introduced in Windows 7 and Windows Server 2008 R2 to improve security and ease of management.

2