This document discusses building a database as a service for a private cloud. It outlines setting up database service packages, automatically provisioning servers and database installations, monitoring databases for billing purposes, a self-service portal for database management, and service level agreements for databases. It also mentions reporting database usage and trend analysis.

1. Building Database as a Service
for Private Cloud
By Esendal Yasin
And Mert Biyikli
MEA HQ Lead Architects

2. Agenda
• Building a Database Services Catalog
• Private Cloud Database Service Packages
• Automatic Provisioning of Server and DB
Installation
• Private Cloud Database Monitoring for Charge
Back (Billing)
• Self-Care Portal for Private Cloud Database
Management
• SLAs for Private Cloud Databases
• DB Usage Reporting with Trend Analysis

3. Building a Database Services Catalog
Reporting
Service
BI
Service
Data
W/H
Service
Development
Shared Infrastructure
Data Services
Production Data Center A Production Data Center B Mgmt
Autopilot
Shared Support
Monitoring
Data
Warehouse
Best
Practices
Shared Processes
Release
Pipeline
Sprint &
Scrum
Capacity
Planning
Shared Components
Escalations
Support
Tools
Libraries
On-boarding
Metering & Billing
Developer Center

4. Private Cloud Database Service
Packages 1/2
Service Design – Best Practices
• Deployment
• Upgrades
• Monitoring
• Reporting
• Supportability, tracing, debugging
• Service SLA
• Security review
• Legal review
• Escalations
• Customer interaction
Microsoft Confidential

5. Private Cloud Database Service
Packages 2/2
Database of Microsoft Products
Database of Third Party Products
Database of In-House Products
HAOptions
DROptions
Size
#ofConcurrentUsers

6. Automatic Provisioning of Server and
DB Installation
Machine 1
VM 2
SQL Server
SV
SQL
DB
SQL
DB
VM 1
SQL Server
SV
SQL
DB
SQL
DB
Machine 2
VM 4
SQL Server
SV
SQL
DB
SQL
DB
VM 3
SQL Server
SV
SQL
DB
SQL
DB
Utility: Provisioning (databases, accounts, roles, …), Metering, and Billing
Scalability and Availability: Fabric, Failover, Replication, and Load balancing

7. Private Cloud Database Monitoring for
Charge Back (Billing) 1/2

8. Private Cloud Database Monitoring for
Charge Back (Billing) 2/2

9. Self-Care Portal for Private Cloud
Database Management
• Creating Maintenance Plan
– Check DB Integrity
– Shrink Database
– Reorganize Index
– Update Statistics
– Clean Up History
– Execute SQL Server Agent Job
– Backup (Full-Differential-Transaction Log)
• Resource Governor
• Policy Management

10. SLAs for Private Cloud Databases
Service Level Agreement (SLA)
This document will serve as both a template and an example of a Service Level Agreement (SLA) between two parties. It can be modified for use in your environment, or it can serve as an example for
constructing your own SLA. The SLA shown here is just an example; many example tables have only one line but in reality would need more. Ensure that whatever SLA you implement covers all areas that
are required by your company and, if necessary, is certified by your legal department, especially if the SLA involves external vendors.
The SLA as shown here as these basic sections:
 Introduction
 Services Provided
 Signatures
The Introduction and Signatures sections are self-explanatory. The Services Provided section should include such things as:
 Availability
The key to any SLA is how availability is defined, as well as how it will be achieved and the desired amount of availability.
 Notification for updates
This will detail the amount of lead time that the people supporting the systems will need to be notified in the event that an update or something of that nature will need to be installed on the systems.
 Support information
This section will outline all relevant support information: how the systems will be supported, what will be supported, the hours of coverage, how to report problems and escalate, contacts, etc.
 Metrics
Regular status should be detailed—how it will be provided, and what will be in the report.
 Cost
The cost section outlines how the services will be paid for, and who is responsible for what.

11. DB Usage Reporting with Trend
Analysis
11

12. Q & A