Download - IPD - SQL Server Version 1.2
-
8/13/2019 IPD - SQL Server Version 1.2
1/41
Microsoft
SQL Server
2008 andSQL Server2008 R2
Infrastructure Planning and Design
Published: February 2009Updated: January 2012
-
8/13/2019 IPD - SQL Server Version 1.2
2/41
What Is IPD?
Guidance that clarifies and streamlines the planning anddesign process for Microsoft infrastructure technologies
IPD: Defines decision flow
Describes decisions to be made
Relates decisions and options for the business
Frames additional questions for business understanding
IPD guides are available at www.microsoft.com/ipd
http://www.microsoft.com/ipdhttp://www.microsoft.com/ipd -
8/13/2019 IPD - SQL Server Version 1.2
3/41
Getting Started
Microsoft
SQL Server
2008 andSQL Server2008 R2
-
8/13/2019 IPD - SQL Server Version 1.2
4/41
Purpose and Overview
Purpose
To provide guidance for designing a Microsoft SQL Server2008 infrastructure, or where applicable, a Microsoft SQL
Server 2008 R2 infrastructure
Overview
Microsoft SQL Server 2008 architecture
Microsoft SQL Server 2008 infrastructure design process
-
8/13/2019 IPD - SQL Server Version 1.2
5/41
What Is Microsoft SQL Server 2008?
Microsoft SQL Server 2008 is a databasesolution that includes four primarycomponents:
Database Engine
Integration Services
Analysis Services
Reporting Services
Microsoft SQL Server 2008 R2 includes afifth component:
Master Data Services
-
8/13/2019 IPD - SQL Server Version 1.2
6/41
Microsoft SQL Server 2008 - Out of Scope
The guide does not address the following:
In-place upgrades
Side-by-side upgrades
Developer, Express, Compact, Evaluation, and Parallel
Data Warehouseeditions of SQL Server
SharePoint integration
Database design
-
8/13/2019 IPD - SQL Server Version 1.2
7/41
Whats New in Microsoft SQL Server 2008 R2
Microsoft SQL Server 2008 R2 has expandedreporting and analytics and two newpremium editions:
SQL Server 2008 R2 Datacenter
SQL Server 2008 R2 Parallel Data Warehouse
In addition:
Master Data Services
Improved application and multiserver management
-
8/13/2019 IPD - SQL Server Version 1.2
8/41
SQL Server 2008 Decision Flow
MDT SCM ITA
-
8/13/2019 IPD - SQL Server Version 1.2
9/41
Example SQL Server Architecture
MDT SCM ITA
-
8/13/2019 IPD - SQL Server Version 1.2
10/41
Step 1. Determine Project Scope
The project scope will be determined in order toalign the goals of the project with the businessmotivation:
Task 1: Determine applications in scope
The results of this step will be used to determinewhich SQL Server roles will be required
-
8/13/2019 IPD - SQL Server Version 1.2
11/41
Step 2. Determine Which Roles Will BeRequired
The product roles required to deliver the businessrequirements and desired functionality will beidentified to:
Task 1: Determine whether a Database Engine will be required
Task 2: Determine whether SQL Server Integration Services will be
required
Task 3: Determine whether SQL Server Analysis Services will be
required
-
8/13/2019 IPD - SQL Server Version 1.2
12/41
Step 2. Determine Which Roles Will BeRequired (Continued)
The product roles required to deliver the businessrequirements and desired functionality will beidentified to:
Task 4: Determine whether SQL Server Reporting Services will be
required
Task 5: Determine whether SQL Server Master Data Services will be
required
-
8/13/2019 IPD - SQL Server Version 1.2
13/41
Step 3. Design the SQL Server Database EngineInfrastructure
The database requirements will be gathered and thedatabase infrastructure will be designed from thoserequirements to:
Task 1: Determine capacity and performance requirements:
Storage needs should be calculated for the database, transaction
log, indexes, and tempdb database
After estimating the database size with the formula provided in
the guide, add about 5 percent for database overhead
Estimate IOPS and throughput as accurately as possible sinceboth of these can cause performance degradationif not properly calculated
-
8/13/2019 IPD - SQL Server Version 1.2
14/41
Step 3. Design the SQL Server Database EngineInfrastructure (Continued)
The database requirements will be gathered and thedatabase infrastructure will be designed from thoserequirements to:
Task 2: Determine whether to place the database in a new orexisting instance
A separate instance might be required because of memory
isolation needs; different fault tolerance, authentication, or
security concerns; or regulatory or support requirements
Task 3: Determine whether to place the instance on a new orexisting server running SQL Server
However, each additional instance adds overhead
-
8/13/2019 IPD - SQL Server Version 1.2
15/41
Step 3. Design the SQL Server Database EngineInfrastructure (Continued)
The database requirements will be gathered andthe database infrastructure will be designed fromthose requirements to:
Task 4: Determine the number of servers
Task 5: Determine placement of each new instance
Task 6: Select the server hardware
-
8/13/2019 IPD - SQL Server Version 1.2
16/41
Step 4. Design the SQL Server IntegrationServices Infrastructure
If it was determined that SQL Server IntegrationServices (SSIS) is required in the organization, theSSIS infrastructure will be designed in this step to:
Task 1: Determine resource requirements
Task 2: Decide where the Integration Services packageswill be stored
Task 3: Determine the number of SSIS servers required
Task 4: Determine placement
-
8/13/2019 IPD - SQL Server Version 1.2
17/41
Step 5. Design the SQL Server AnalysisServices Infrastructure
If it was determined that SQL Server AnalysisServices (SSAS) is required in the organization, theSSAS infrastructure will be designed in this step to:
Task 1: Determine resource requirements SSAS uses OLAP databases, or cubes, stored on the file system
Processing of OLAP databases is read- and write-intensive
Product group recommends 48 GB of memory per processor
core
-
8/13/2019 IPD - SQL Server Version 1.2
18/41
Step 5. Design the SQL Server AnalysisServices Infrastructure (Continued)
If it was determined that SQL Server AnalysisServices (SSAS) is required in the organization, theSSAS infrastructure will be designed in this step to:
Task 2: Determine SQL Server version
Task 3: Decide whether scalable shared databases will beused
Task 4: Determine scaling needs
Task 5: Decide whether to cluster
Task 6: Determine placement
-
8/13/2019 IPD - SQL Server Version 1.2
19/41
Step 6. Design the SQL Server ReportingServices Infrastructure
If it was determined that SQL Server ReportingServices (SSRS) is required in the organization, theSSRS infrastructure will be designed in this step to:
Task 1: Determine resource requirements. Depends on: Disk storage needed for SSRS databases
Memory: 24 per processor core
Task 2: Determine placement of the report serverdatabases
Databases can be hosted either on the Reporting Servicesserver or on a remote database server
-
8/13/2019 IPD - SQL Server Version 1.2
20/41
Step 6. Design the SQL Server ReportingServices Infrastructure (Continued)
If it was determined that SQL Server ReportingServices (SSRS) is required in the organization, theSSRS infrastructure will be designed in this step to:
Task 3: Determine scaling and fault-tolerance approach: Load balancing for both scale out and fault tolerance
Clustering for report server databases
Task 4: Determine placement of the SSRS server
-
8/13/2019 IPD - SQL Server Version 1.2
21/41
Step 7. Design the SQL Server Master DataServices Infrastructure
If it was determined that SQL Server Master DataServices is required in the organization, theinfrastructure will be designed in this step to:
Task 1: Determine resource requirements
Task 2: Determine the scaling and fault-tolerance approach
-
8/13/2019 IPD - SQL Server Version 1.2
22/41
Step 7. Design the SQL Server Master DataServices Infrastructure (Continued)
If it was determined that SQL Server Master DataServices is required in the organization, theinfrastructure will be designed in this step to:
Task 3: Determine Placement of the Master Data ServicesDatabase
Task 4: Determine Placement of the Master Data ServicesWeb Server
-
8/13/2019 IPD - SQL Server Version 1.2
23/41
Summary and Conclusion
The SQL Server 2008 guide has outlined the processfor planning the SQL Server infrastructure:
Choices of roles needed
Server resources
Scaling
Fault tolerance
Provide feedback to [email protected]
mailto:[email protected]:[email protected] -
8/13/2019 IPD - SQL Server Version 1.2
24/41
Find More Information
Download the full document and other IPD guides:www.microsoft.com/ipd
Contact the IPD team:
Access the Microsoft Solution Accelerators website:
www.microsoft.com/technet/SolutionAccelerators
http://www.microsoft.com/ipdmailto:[email protected]://www.microsoft.com/technet/SolutionAcceleratorshttp://www.microsoft.com/technet/SolutionAcceleratorsmailto:[email protected]://www.microsoft.com/ipd -
8/13/2019 IPD - SQL Server Version 1.2
25/41
Questions?
-
8/13/2019 IPD - SQL Server Version 1.2
26/41
Addenda
Example SSIS Configuration
Example SSAS Configuration
Example SSRS Configuration
Example Master Data Services Configuration
Job Aids Benefits of using the SQL Server 2008 guide
IPD in Microsoft Operations Framework 4.0
-
8/13/2019 IPD - SQL Server Version 1.2
27/41
Example SSIS Configuration
-
8/13/2019 IPD - SQL Server Version 1.2
28/41
-
8/13/2019 IPD - SQL Server Version 1.2
29/41
Example SSRS Configuration
-
8/13/2019 IPD - SQL Server Version 1.2
30/41
Example Master Data Services Configuration
-
8/13/2019 IPD - SQL Server Version 1.2
31/41
Job Aids
Step 1.Use the table below to record business applications in theproject scope.
Table A-1. Requirements Gathering
Requirement description Requirement results
Name of business applications
-
8/13/2019 IPD - SQL Server Version 1.2
32/41
Job Aids (Continued)
Step 2.Use the table below to record information relative to therequired SQL Server roles.
Table A-2. SQL Server Roles Data Gathering
Requirement description Requirement results
Names of relational or OLTP databases required
Names of data warehouse databases required
SSIS required?
SSAS required?
SSRS required?
* requires Database Engine also
Master Data Services required?
* requires Database Engine also
-
8/13/2019 IPD - SQL Server Version 1.2
33/41
Job Aids (Continued)
Step 3.Use the table below to record information relative to the SQLServer Database Engine.
Table A-3. SQL Server Database Engine Data GatheringRequirement description Requirement results
Disk storage requirements
IOPS and throughput requirements
Database in new or existing instance?
Will instance reside on existing server running SQL
Server or new server?
Number of servers required to support scale-out
options, if selected
Number of servers required to support fault-
tolerance option, if selected
Failover clustering protection required?
In which office or geographical location will instance
be placed?
-
8/13/2019 IPD - SQL Server Version 1.2
34/41
Job Aids (Continued)
Step 3.Use the table below to record information relative to the SQLServer Database Engine.
Table A-3. SQL Server Database Engine Data Gathering(Continued)Requirement description Requirement results
Will instance be on physical server or virtualized
environment?
Number of CPUs required
Required architecture
Required processor speed
Amount of memory required
Disk subsystem configuration
-
8/13/2019 IPD - SQL Server Version 1.2
35/41
Job Aids (Continued)
Step 4. Use the table below to record information relative to the SSISinfrastructure.
Table A-4. SQL Server SSIS Infrastructure Data Gathering
Requirement description Requirement results
Does each component of the system meet the
capacity and performance requirements?
Source data type
Destination data type
SSIS server version
Name of SQL Server instance or file share where
packages are stored
Database Engine required?
Number of SSIS servers
SSIS server: virtualized or physical environment?
SSIS - SQL Server role coexist with other SQL
Server roles on same server?
-
8/13/2019 IPD - SQL Server Version 1.2
36/41
Job Aids (Continued)
Step 5. Use the table below to record information relative to the SSASinfrastructure.
Table A-5. SQL Server SSAS Infrastructure Data Gathering
Requirement description Requirement results
Disk storage space requirements
SSAS server version
Will scalable shared databases be used?
What are scaling needs? (scale up or scale out)
Will failover clustering be used?
SSAS server: virtualized or physical environment?
SSAS - SQL Server role coexist with other SQL
Server roles on same server?
-
8/13/2019 IPD - SQL Server Version 1.2
37/41
Job Aids (Continued)
Step 6. Use the table below to record information relative to the SSRSinfrastructure.
Table A-6. SQL Server SSRS Infrastructure Data Gathering
Requirement description Requirement results
Record database requirements (size of the
ReportServer and ReportServerTempDB
databases)
Databases hosted locally or on a remote databaseserver?
Which databases are hosted locally or on a remote
server?
Number of servers to support SSRS
SSRS SQL Server coexist with other SQL Server
roles on same server?
SSRS server: virtualized or physical environment?
-
8/13/2019 IPD - SQL Server Version 1.2
38/41
Job Aids (Continued)
Step 7. Use the table below to record information relative to the
Master Data Services infrastructure.
Table A-7. SQL Server Master Data Services Infrastructure DataGatheringRequirement description Requirement results
Estimated Master Data Services database size
Number of concurrent users
Number of servers to support fault tolerance and
scaling requirements
Databases hosted locally or on a remote database
server?
Which databases are hosted locally or on a remote
server?
Master Data Services Web server coexist with otherSQL Server roles on same server?
Master Data Services Web server: virtualized or
physical environment?
-
8/13/2019 IPD - SQL Server Version 1.2
39/41
Benefits of Using the SQL Server 2008 Guide
Benefits for Business Stakeholders/Decision Makers Most cost-effective design solution for implementation
Alignment between the business and IT from the beginning of the designprocess to the end
Benefits for Infrastructure Stakeholders/Decision Makers
Authoritative guidance Business validation questions ensuring solution meets requirements of business
and infrastructure stakeholders
High-integrity design criteria that includes product limitations
Fault-tolerant infrastructure
Proportionate system and network availability to meet business requirements
Infrastructure thats sized appropriately for business requirements
-
8/13/2019 IPD - SQL Server Version 1.2
40/41
Benefits of Using the SQL Server 2008 Guide(Continued)
Benefits for Consultants or Partners Rapid readiness for consulting engagements
Planning and design template to standardize design and peer reviews
A leave-behind for pre- and post-sales visits to customer sites
General classroom instruction/preparation
Benefits for the Entire Organization Using the guide should result in a design that will be sized, configured,
and appropriately placed to deliver a solution for achieving statedbusiness requirements
-
8/13/2019 IPD - SQL Server Version 1.2
41/41
IPD in Microsoft Operations Framework 4.0
Use MOF with IPD guides to ensure that people and processconsiderations are addressed when changes to an organizations ITservices are being planned.