1. Microsoft SQL Server 2014 for Oracle DBAs Module 1
11: Monitoring and performance tuning
Microsoft SQL Server 2014 for Oracle DBAs Module 1
Database and instances

2. Understanding database limits
40074
Module Overview
2: Database and instances
Understanding database limits

3. Lesson 1: Terminology concepts
40074
Lesson 1: Terminology concepts
2: Database and instances
Demonstration: Directory structure

4. Common ground in database management systems
40074
Common ground in database management systems
2: Database and instances PC
Server
Storage
INSTANCE
DATABASE
CLIENT
Memory
Process
CPU
Temp
Log
Control
System
Data
A database management system encompasses at least one database and instance.
A database is a set of physical files that store application and system data.
An instance consists of the hardware resources of the system (primarily memory and CPU utilization) that facilitate data access for the end user.

5. Database and instance implementations
40074
Database and instance implementations
2: Database and instances
Oracle 12c
SQL Server 2014
Database
Schema
Object
Instance
Host Machine

6. Demonstration: Starting SQL Server instances
40074
Demonstration: Starting SQL Server instances
2: Database and instances
In this demonstration you will see how to:
Stop and start service using the SQL Server Configuration Manager
Stop and start services using the command prompt
Students may have to execute the net start command using a command prompt as Administrator or they could get an Access is denied error message.
Ensure you are familiar with running command prompts elevated on the supported operating systems.
Demonstration Steps
Click Start → All Programs → Microsoft SQL Server 2014 → Configuration Tools → SQL Server Configuration Manager.
Click SQL Server Services.
Right-click the SQL Server(INST01) service.
Note: You may stop, pause, or restart the service.
Click Stop to stop the service. Watch the service icon change to a red button. This shows that the service has stopped.
Keep the SQL Server Configuration Manager window open.Click Start → Run, and type cmd to open a command prompt.
Note: You may receive an “Access is denied” error message. If so, run the command prompt elevated.
To start a named instance, use the following syntax net start MSSQL$<instance name> by typing Net start MSSQL$INST01.
If the service is already started, then a message will be provided with no impact on the service already running. The statement is: The requested service has already been started.
Wait until the message reports that the “service was started” successfully.
Move back to the SQL Server Configuration Manager window and notice that the instance still seems to be stopped.
Click the refresh button in the toolbar to have the Windows Management Instrumentation (WMI) update the services.
The instance now shows the green arrow indicating that it is running.
(More notes on the next slide)

7. Demonstration: Managing SQL Server Objects
40074
Demonstration: Managing SQL Server Objects
2: Database and instances
Connect to a database engine
View the properties of an instance in Configuration Manager
Review a database in object explorer
Connect to another database engine
Review associated registry keys for SQL Server installations
Demonstration Steps
Click Start → All Programs → Microsoft SQL Server 2014 → SQL Server Management Studio.
If prompted to connect to a server, press Cancel.
In Object Explorer, click Connect, and then click Database Engine.
Choose the INST01 instance for the Server name.
To connect using Windows Authentication, click Connect.
Once the instance is added, you can view its objects and settings within SQL Server Management Studio Object Explorer.
Go back to SQL Server Configuration Manager.
Right-click the instance INST01 and click Properties.
On the Log On tab, notice the service Account Name and Password which this instance runs under a security context. It should always be a least privileged account with just enough permission to execute an instance of SQL Server.
For more information on setting up service accounts, see the Services and Service Accounts Security Planning Guide at
Click the Service tab.
Review the Binary Path property and note that the instance points to the same path we saw earlier from Windows Explorer.
Review the Start Mode property. Normally this is set to Automatic, but may be set to Disabled or Manual.
Select the FILESTREAM tab. This will be covered in a later section to address large objects.
Select the Advanced tab.
Review the Data Path, File Version, and Instance ID properties.
(More notes on the next slide)

8. Demonstration: Directory structure
40074
Demonstration: Directory structure
2: Database and instances
Review associated registry keys for SQL Server installations
Demonstration Steps
Open Windows Explorer to view the file system. If SQL Server instances are installed in the default installation location (options will be shown later in Module 7), then each instance will appear under C:\Program Files\ Microsoft SQL Server.
Shared components are in subdirectories based on their version number.
SQL Server 2000 = 80
SQL Server 2005 = 90
SQL Server 2008 = 100
SQL Server 2012 = 110
SQL Server 2014 = 120
Go to the C:\Program Files (x86)\Microsoft SQL Server\120\Tools\Binn\ManagementStudio directory and note the presence of ssms.exe.
Each database engine instance has its own directory, as does each additional component. SQL Server 2014 provides a clear representation of the components by prefixing the directories with MS, followed by a two or three letter code (Analysis Services = AS, Reporting Services = RS, and SQL Server database engine = SQL). Other directories most likely represent component versions prior to SQL Server 2014.Open Windows Explorer.
Go to the C:\Program Files\Microsoft SQL Server\MSSQL12.INST01\MSSQL\Binn directory and note the presence of sqlservr.exe.
Browse to the C:\Program Files\Microsoft SQL Server\MSSQL12.INST02\MSSQL\Binn directory and note the presence of sqlservr.exe here as well.
Each instance of SQL Server has its own executable and can be patched separately.
SQL Server Management Studio is a shared tool which is used across all instances.Go to Start → Run. Type regedit in the text box and press Enter. The registry information will be displayed.
Go to HKey_Local_Machine → Software → Microsoft → Microsoft SQL Server →
(More notes on the next slide)

9. Lesson 2: Client interaction with database and instance
40074
Lesson 2: Client interaction with database and instance
2: Database and instances
Demonstration: Reviewing network connections

10. Oracle communications
40074
Oracle communications
2: Database and instances
Oracle connections
Client
Person
System
Application
Layer
Oracle Net
Foundation
Oracle
Protocol
Support Layer
Database Server
Listener (defined by listener.ora may implement TNSnames.ora
Oracle Instance
Oracle Protocol
Storage System
Data Storage
Key components in the interaction of the user (client) with the database environment

11. SQL Server communications
40074
SQL Server communications
2: Database and instances
SQL Server connections
Client
Person
System
Application
Layer
SQL Server
Network
Interface
Protocol
SNAC network libraries
Database Server Engine
TDS Endpoints (Shared memory, TCP/IP, named pipes, VIA, DAC)
Relational Engine
Tabular Data
Stream (TDS)
Packet
SQL Server Network Interface (SNI) Layer
Storage System
Data Storage
Ensure the students understand the difference between the network configuration and client configuration when it comes to the protocols.
Key components in the interaction of the user (client) with the database environment

12. Demonstration: Reviewing network connections
40074
Demonstration: Reviewing network connections
2: Database and instances
In this demonstration you will see how to:
Analyze network protocols
Review TCP/IP settings
Analyze client protocols

13. Lesson 3: Understanding database limits
40074
Lesson 3: Understanding database limits
2: Database and instances
Database system space

14. Database Capacities on Windows Server 2012 R2
40074
Database system space
2: Database and instances
Database Capacities on Windows Server 2012 R2
Oracle 12c
SQL Server 2014
Minimum data block size
2 KB
8 KB
Maximum data block size
16 KB (Linux and Windows) or 32 KB (other OSs)
Maximum file size
Operating system dependent. Limited by maximum operating system file size; typically 222 or 4 MB blocks
16 TB
Maximum number of files
65, 533
32, 767
Maximum database size
4 PB
(65,536 * 64 GB)
524 PB
Maximum control file size
logical blocks
N/A
Instances per server
Limited by host resources
50 for all editions of SQL Server
Maximum database extent
4 GB
64 KB
Maximum number of tablespaces
65,536
32,767 (filegroups – see Module 2)
Maximum log file size
2 GB (operating system limit)
2 TB
Source for Oracle Database 12c:
Source for SQL Server 2014:

15. © 2014 Microsoft Corporation. All rights reserved
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.