Escolar Documentos
Profissional Documentos
Cultura Documentos
Planning time spent in I/O Configuration would have significant payback Normal I/O Performance guidelines apply
Minimally, size for the sum of all work load being consolidated including growth Be careful
An misbehaving application might use up DB and Log space planned for other applications An upper limit specification might be appropriate for some DBs
Considerations
Isolation at physical disk level may not be practical Focus on ensuring healthy disk latency
1 - 5 ms for Log (Ideally 1 ms or better) 5 - 20 ms for Data (OLTP) (Ideally 10 ms or better) <=25-30 ms for Data (DSS)
Be aware of spindle sharing with other servers and, ideally, avoid if possible
Keep Backup Files on separate spindles Safeguard against Cache loss (battery back up) Particularly for Log Devices Watch cache read write usage settings Use multiple channels if available
ge-top-10.mspx
Processors
Best Practice: Place a memory ceiling on each relational server instance To ensure a certain amount of memory resources set min server memory
Be aware that SQL does not acquire memory on startup, memory is acquired on demand (this is a behavior change from SQL 2000 64-bit)
Best Practice: Grant the SQL Server service account Lock pages in memory privilege
Prevents OS paging of SQL buffers pool memory under memory pressure
Single instance of SQL Server Multiple SQL Server instances sharing the server
When other components (AS, SSIS, RS) co-reside with the relational server
instance (Msql)
Ensure Msql < Total Server Memory ~1GB (per 8-16GB) for OS
Improved placement of objects in local cache Per-node lazywriter, free list and checkpointing Per-node resource management (threads) Per-node IO completion port
A SQL connection will remain on the same NUMA node for its lifetime
Potential for leveraging local cache for all of its tasks Soft NUMA provides the ability to direct specific connections to
specific nodes
NUMA: Be Careful
other CPUs
Common to see only one busy set of nodes and remainder of server idle
Avoids AS potentially grabbing all local memory for one node Avoids filesystem cache from stealing pages disproportionately from a single node which could create a SQL node starved of local pages
TempDB Usage
DBCC CHECKDB - small change Internal objects: work file (hash join, SORT_IN_TEMPDB) - CTEs Internal objects: work table (cursor, spool) - small changes Large object (LOB) variables Service Broker Temporary objects: global/local temp table, table variables Temporary objects: SPs and cursors - small changes Version store: General Version store: MARS Version store: Online index, mapping index, sort operations Version store: Row version based isolation levels Version store: Triggers XML
High Availability
Failover Clustering Database Mirroring Log Shipping
Log Shipping
Only User Databases can be Log Shipped Master DB
System Configuration
Logins
MSDB
SQL Agent Jobs
Backup History
DTS Packages saved in SQL Server
Log Shipping
Master Model
Databases Safe
MSDB
Only User Databases can be Log Shipped
AdventureWorks
TempDB
Failover Clustering
Pros
Very high availability Quick failover (5-90 seconds) Same IP Address All databases are safe. TempDb is cleared. Standard Edition can now be setup as a 2 node cluster. Enterprise Edition can now be setup as a 8 node cluster.
Cons
Hardware must be on Windows HCL Cost SAN is Point of Failure Can not protect against database Corruption Sensitive to Domain Controller outages SQL Server Service Pack application requires instance downtime Transactions in progress are rolled back Shared location
Failover Clustering
Master Model
Databases Safe
MSDB
TempDB is cleared on failover
AdventureWorks
TempDB
Database Mirroring
Synchronous with a witness Mirror acknowleges before commit to client Automatic Failover Mirror and Witness not reachable, DB goes offline
Database Mirroring
Master Model
Databases Safe
MSDB
Only User Databases can be Mirrored
AdventureWorks
TempDB
Backup / Restore
STSADM.exe
Site Deleted (sites are not in Recyacvle Bin)
Backup/Resore to another Server Farm
STSADM.exe o backup directory \\moss\moss_backup -backupmethod full
Site
STSADM.exe -o backup -url http://intralot-portal -filename <filepath>.dat overwrite
All MySites
STSADM.exe -o backup -url http://mysites -filename c:\moss_backup\mysites.dat
overwrite
Reporting Services
WSS 2007
Reporting Services Add-in
SSRS 2005
SP2 Report Server
Report Management UI
Security Extension
Catalog Management
SharePoint Content DB
Report Server DB
RS Database Integration
Run Report
Yes
Exists ?
Yes
Master ?
RS - Security Mapping
CreateReport( )
CreateSchedules operation
Report Builder
RS - Security Modes
Windows User
NonWindows User
SSRS SP2
SharePoint Central Administration v3 Writable from Central Administration, Read by all Web Applications SSP1 SSP1
60MB
100MB
Site Collection for Central Administration Web Site Hosts Configuration Information Common to all members of the Farm.
10MB
100MB
SSP1_DB SSP1_Search_DB
10MB 3MB
100MB 75GB
Shared Services Providing Content DB Responsible for storing search related data from indexing (Property Store, URL Maps) Content Database for SSP administration site. Crawl Database of SharePoint Help FIle
SSP1_WSS_Content
SSP1
14MB
100MB
WSS_Search_ServerName
Central Administration
60MB
100MB
The Search_DB also hosts the query log used for query reporting and analysis!
Microsoft IT
12TB of SharePoint data. 83GB index files (0.67 % of Content) 243GB Search database (1.97 % of Content)
2.64%
More Information
SQLRAP - SQL Risk Assesment Program, delivered by Premier Support Services, ask your Technical Account Manager (TAM) SQL Server Customer Advisory Team: http://blogs.msdn.com/sqlcat Troubleshooting Performance Problems in SQL Server 2005 http://www.microsoft.com/technet/prodtechnol/sql/2005/tsp rfprb.mspx SQL Server User Group http://www.sqlpass-swiss.org/