Você está na página 1de 20

v

info@kastechssg.com www.kastechssg.com
Installation & Build v

SQL SERVER VERSIONS


Cluster Installation (Active-Active / Active-Passive).
2008,2008R2,2012,2014,2016

Installation of single instance /multi- Applying patches ( Security patches, Service Packs,
instances (max 50) Cumulative Updates) on standalone and multiple
nodes cluster.

Setting up Production, Development , SIT,


Creating databases , logins and grant permissions to
UAT servers.
users.

Assessment of storage space depends on Creation of Maintenance plans ( application jobs,


characteristics of Application. Backup jobs, index, update stats , database
integrity check , database shrink jobs)

DAN ( Database Area Network i.e. Multi


application databases on single node) Database Migration and Upgrades
Dedicated servers (Single Application
databases on single node)

info@kastechssg.com www.kastechssg.com
Security Management v
Creating users and Assigning permissions based on level of databases Access.
Hardening of Operating System as mentioned below:

Controlling ADMIN access to the database. Regular Audit checkups.


Increase role based access instead of
ADMIN( sysadmin) role.

Remove unwanted users who are not Enable fire wall settings.
authorized to login and perform specific
task. Mode of Authentication (Windows
and SQL mode).

Data Encryption between Application and


Update Security Patches on time. database ( Symmetric and Asymmetric keys),
Certificates, Transparent data Encryption , Cell
level Encryption , Column level Encryption ( SQL
2016).

info@kastechssg.com www.kastechssg.com
High Availability v

Configuration and troubleshooting of following mechanisms.

Log shipping Database Mirroring

Failover Clustering Replication ( Object Level)

Always On

info@kastechssg.com www.kastechssg.com
Database Maintenance and Monitoringv

Maintaining Data highly available for the customers. Migration of databases from Production to UAT/ DEV.

Regular database health checkup using automated scripts Deploying scripts on Production databases as per
for critical tier-1 applications. business need.

Designing & Performing database maintenance


tasks (Rebuild Index, Updates stats, Integrity check) 24/7 on call production support.
during non business hours and weekends.

Designing and monitoring database backup and recovery


Daily/ Emergency data refreshes as per customer request.
models.

Implementing Change Requests and Work Orders on both


Disk management and monitoring space in disks.
Production and Non Production databases.

info@kastechssg.com www.kastechssg.com
Performance Tuning v

Interacting with Resolving space issue Resolving Performance monitoring Stats Maintenance
Application team to by adding space to Tempdb and resolving CPU,
resolve performance disks and shrinking Issues. Memory Utilization bottle
issues. Database Log space. necks.

10 09 08 07 06 05 04 03 02 01

Query Tuning for Dynamic Management Resolving I/O Resolving Index Maintenance
long running Views (DMV's), Stored , hardware, Blocking, Locking
queries and Procedures (SP’s) , Regular Network and Deadlock
execution plan to DBCC (Database issues. issues.
view the query Consistency Checks to
design. monitor performance
bottle necks.

info@kastechssg.com www.kastechssg.com
Third Party Tools v

Robo Copy : To copy data and files across SQL Spot light tool By Quest : To monitor performance of
the servers. SQL server

SCOM : Ticketing Tool. Light Speed by Quest : For backup and recovery

SQL COMPARE by Redgate : Deploy the NetBackup : To archive the backups and retrieve
changes with out need of database when needed.
recovery between the servers.

info@kastechssg.com www.kastechssg.com
Documentation v

Service packs and Logins and


List of Production Installation and
hot fixes applied to roles that has
and Non Production upgrades on servers.
servers. been removed.
servers.

Filter out the


Process Number of Number of Applications ( Tier-1,
Improvements. database servers. Application servers. Tier-2, Tier-3) depends
up on criticality.

info@kastechssg.com www.kastechssg.com
Log shipping v

Database high availability.

Database primary (source) server and standby (target) server.

Availability of two copies- Primary database and Secondary database.

Log backups
Copy Backup files secondary Restored Logs to
server secondary database

Primary database Secondary database


on primary server on secondary server

Backup performed by SQL server Copy and restore performed by SQL


agent job on the secondary server server Agent jobs on the secondary server

info@kastechssg.com www.kastechssg.com
Database Mirroring v

Client Client Client Client

Network

SQL Server 2008 SQL Server 2009

Adventure Adventure
Principal Works DB Works DB
Server
translog translog

SQL Server xyz

Witness
Server MSDB DB

info@kastechssg.com www.kastechssg.com
Database Mirroring v

• Disaster recovery and high availability technique


• Two SQL Server instances on the same or different machines
• Create primary instance of SQL Server called the principal
• Create mirrored instance called the mirror.
• Principal and Mirrored instance are always in Sync
• In special cases, there can be a third SQL Server instance that acts as a witness

info@kastechssg.com www.kastechssg.com
Always On v

Windows Server Failover Clustering (WSFC) Cluster

WSFC Resource Group for ‘MyAg’ Availability Group

Node 01 Node 02 Node 03 Node 04 Node 05

SQL Server SQL Server SQL Server SQL Server SQL Server
Instance Instance Instance Instance Instance

‘MyAg’ Availability Group


Node 01
Primary Secondary Secondary Secondary Secondary
Replica Replica Replica Replica Replica

info@kastechssg.com www.kastechssg.com
Always On v

The Always On Availability Groups feature is a high-availability and disaster-recovery solution that provides an enterprise-level
alternative to database mirroring.

Always On Availability Groups is a database mirroring technique that allows


administrators to pull together a group of user databases that can failover together.

SQL SERVER 2012 : 4 (secondary Readable Replica) + 1 (Primary Replica)

SQL SERVER 2014 : 8 (Secondary Readable Replica) + 1 (Primary Replica)

Availability Group

info@kastechssg.com www.kastechssg.com
SQL SERVER 2016 new features v

TempDB : Multiple tempDB database files can configured at the time of installation which is nit supported in
previous versions.

Query Store : It stores query texts, execution plans, performance metrics with in the
database which allows to troubleshoot performance issue easily.

Temporal Tables : These are history tables which records complete data changes
with respective to date and time.

JSON : JSON is supported in SQL SERVER to import, export and storing.


SQL
SERVER
Polybase : It integrates sql server query engine with external data in Azure
and Hadoop blob storage.

Stretch Database : It lets to store achieve data in to cloud (AZURE) and current data in Local
( On Premises).

Live Query Statistics : SQL server is providing ability to view execution plan when the query is in active state
which helps to find cause of long running queries.

info@kastechssg.com www.kastechssg.com
SQL SERVER 2016 new features v
Security Features

Row Level Security : Data access can be restricted at database engine level

Dynamic Masking :Masked data is hidden to users and users who is having UNMASK
permission can view it.

Always Encrypted : When application is having dedicated encrypted key it


can access encrypted sensitive data in database.

info@kastechssg.com www.kastechssg.com
Log shipping Vs Mirroring v

Log shipping Mirroring


Primary server, secondary server and monitor server are the Principal server, mirror server, and witness server are the
components in log shipping set up. components involve in database mirroring set up.
Witness server is an optional but it is a must for setting up automatic failover
Monitor server is an optional. since witness is a watchdog instance to check if principal server is working

Log shipping is a manual failover process. Database mirroring is an automatic failover process.

There will not be an automatic application connection Application connection can be redirected automatically
redirection. It has to be redirected manually. with proper configuration.
Log shipping will have multiple secondary databases for the Database mirroring will not have multiple database
synchronization. destinations for mirroring

There will be data transfer latency. There will not be data transfer latency.

In log shipping, secondary database can be used for reporting In database mirroring, mirror database cannot be used for
solution. reporting solution.
Both committed and uncommitted transactions are transferred Only committed transactions are transferred to the mirror
to the secondary database. database.
Log shipping supports both bulk logged recovery model and full
recovery model. Mirroring supports only Full Recovery model.

info@kastechssg.com www.kastechssg.com
Windows Cluster v

Requires more hardware.

A Microsoft service called Microsoft Cluster


Services (MSCS) is used to manage the clustered
server(s).
High Cost.

A SQL Server cluster is a virtual server composed


of two or more server machines (nodes) running
SQL Server.
Complex Design

If one node in the cluster fails, another machine


in the cluster assumes the responsibilities of the
A server cluster is a group of two or more downed node.
physically separate servers working
together to form one "virtual" server.

info@kastechssg.com www.kastechssg.com
Windows Cluster v

Windows 2012
Active Node Passive Node Windows 2012
SQL 2012
SQL 2012

Heartbeat

Windows 2012
SQL 2012

Database Database

Shared Storage
info@kastechssg.com www.kastechssg.com
Windows Cluster v

Active/Passive
• One node controlling SQL Server resources at one time and the other node is continuously in
standby mode waiting for a failover to occur.
• In the event of a failover, the standby node will acquire control of the SQL Server resources.

Active/Active

• Each node in the cluster is running a separate and active instance of SQL Server.
• In the event of a node failure, the other node is able to take control of the failed node's SQL
Server instance. This healthy node will then be running both instances of SQL Server—its own
instance and the failed node's instance.
• This healthy node will then be running both instances of SQL Server—its own instance and the
failed node's instance.

info@kastechssg.com www.kastechssg.com
v

info@kastechssg.com
(832) 651 4843
www.kastechssg.com

Você também pode gostar