Download MOSS 2007 and SQL 2008 - Better Together

Survey
yes no Was this document useful for you?
   Thank you for your participation!

* Your assessment is very important for improving the workof artificial intelligence, which forms the content of this project

Document related concepts

Extensible Storage Engine wikipedia , lookup

Concurrency control wikipedia , lookup

Oracle Database wikipedia , lookup

Tandem Computers wikipedia , lookup

Database wikipedia , lookup

Microsoft Access wikipedia , lookup

Btrieve wikipedia , lookup

Microsoft Jet Database Engine wikipedia , lookup

Team Foundation Server wikipedia , lookup

Database model wikipedia , lookup

Relational model wikipedia , lookup

Clusterpoint wikipedia , lookup

Open Database Connectivity wikipedia , lookup

SQL wikipedia , lookup

Microsoft SQL Server wikipedia , lookup

PL/SQL wikipedia , lookup

Transcript
MOSS 2007 and SQL 2008:
Better Together
Rich Crane and Bob German
Microsoft Technology Center | Boston
Agenda
MOSS Database Review
New SQL 2008 Features Relevant to MOSS
Database Backup Compression
(up to 89% less disk space)
Backup Compression with HA/DR
(restore times up to 50% less with up to 89% less network usage)
Database Mirroring Enhancements
(increase availability while reducing network usage by up to 73%)
Failover Clustering
(much easier to install and manage with increased reliability)
Transparent Data Encryption and Backup Encryption
(encrypt all data seamlessly)
Performance Studio, Central Management, and Policy-Based
Management
(reduce DBA workload)
Additional Resources
R
SharePoint and SQL Server 2008
Any flavor of SharePoint will benefit
Office SharePoint Server 2007 (Standard or
Enterprise)
Windows SharePoint Services 3.0
You need SP1 to make it work!
Existing install: Upgrade to SP1
Clean install: Download SharePoint w/SP1
slipstream
B
SharePoint Databases
Configuration – One per farm, stores information
about the farm topology and settings
Content – Stores all content; it is usual to have
several content databases
WSS Search – Property store for WSS search
SSP Search – Displayable document
properties/metadata for MOSS Search
Single Sign-On – SSO credential mappings
SSP – Other Shared Services such as user
profiles, audiences, etc.
B
Site Collections and Content
Databases
Site
Site
Collection
Top Level
Site
Site
Content DB
Site
Site
Collection
Web
Application
Top Level
Site
Site
Content DB
Farm
Site
Collection
Top Level
Site
Site
Collection
Top Level
Site
Site
Web
Application
B
Content DB
Site
Collection
Top Level
Site
Site
Site
Collection
Top Level
Site
Site
Content Database Example
Company Portal
Document Repository
Team Sites
http://team
http://knowledge
Dept. Portals
SSP Admin
Site
http://portal
B
Web application
Content DB
Site Collection
Central Admin
Site
http://someserver:40203
My Sites
http://my
http://someserver:31415
Database Backups & MOSS
Database Backups are a large part of backing up
SharePoint
They’re not everything … still need to address:
Filesystem:
Installed features
Server configuration, IIS Metabase
Search index
Granular Restores
Recycle bin helps
Data Protection Manager 2007
3rd party tools (AvePoint, Commvault, EMC, etc.)
Still backing up DB’s is the most important
overall and takes up the majority of disk space
B
Compressed By Default
One checkbox
turns on
compression
for all
backups – even
from SharePoint
Central Admin!
B
Backup Compression Example
Content database with ~370K documents
Test
Backup Time (sec) Backup Size (KB)
SQL 2005 SP3
30.98
3,647,646
SQL 2008 (no compression)
29.94
3,648,672
SQL 2008 (w/compression)
16.06
729,314
SQL 2008 with compression ran the backup 48% faster
and used 80% less disk space compared to SQL 2005
Backup Compression can reduce maintenance and
hardware expenditures by reducing disk space for
backups delaying the need for new Content databases
B
(test corpus was 360,000 text files)
DEMONSTRATION
COMPRESSING SHAREPOINT
BACKUPS
B
MOSS High Availability
Load Balancing
Web
Web
Web
Web
Web
Web
Application
SQL
MOSS with SQL
Clustering
SQL
Load Balancing
Mirroring or
Log Shipping
MOSS with SQL
Mirroring or Log
Shipping
B
Web
Web
Web
Web
Web
Web
Application
SQL
SQL
Backup Compression with HA/DR
Database backups are needed for many high
availability and disaster recovery methods such
as Log Shipping and Database Mirroring
Using backup compression can significantly
reduce the time required for initialize and
recovery of your MOSS HA/DR environment
Can significantly improve
Service Level Agreements
(SLA) by reducing
down time
R
Web
Web
Web
Web
Database Mirroring
Popular HA/DR solution
that offers zero-to-minimal
data-loss for your MOSS
database environment
Out-Of-The-Box with
SQL Server 2008 STD/EE
SQL Server 2008 introduces several new features
including log stream compression and bad page protection
Great for low bandwidth & heavy log operations (ex. index rebuild)
Reduce the cost of network bandwidth in your HA/DR environment
Additional protection against failing storage hardware (i.e. disks)
R
Can reduce network utilization or improve Service Level
Agreement (SLA) depending on transaction patterns
Failover Clustering
Rolling upgrade/patch support for SQL Server failover
clusters to minimize downtime
Improve failover cluster setup reliability
Integrated OS cluster health checks
Integrated SQL Server setup health checks
Leverage new setup architecture
Enable for sysprep and slip-stream
Distributed setup on each node – No remote execution
Align with Windows Server 2008 features
R
16-node failover clusters with SQL 2008 EE
More nodes are perfect for shared DB environments
IPV6 and DHCP support
Heterogeneous hardware and iSCSI support
Not aligned with OR dependencies
We
We
bb
We
We
bb
Transparent Data Encryption (TDE)
New Feature In SQL 2008
Transparently encrypts entire database
Encrypt all data seamlessly
This includes backups, transaction logs, and tempdb
Easy to Implement
No programming changes required to implement
Low impact (~3-5% CPU) and can be much lower if most of the
data is stored in memory
Easy to implement with MOSS
Recommended to implement at a Content database
All Sites within Site Collections are protected
No changes to MOSS (i.e. transparent)
Consider moving sites which need encryption to their own SQL
Server instance for performance
R
Performance Studio
New Feature in SQL Server 2008 for Performance
Management (i.e. monitoring and troubleshooting)
SQL Server Performance Dashboard based on system
collection sets reports
Sever Activity
High level SQL Server and system information
Should be turned on all the time
Low overhead (that is, <5 percent)
Query Statistics
Detailed SQL Server information
Drill down to performance issues root cause
Disk Usage - general disk activity information per database
Ability for data to be recorded historically and to be
persisted across service restarts
R
Performance
Studio
Benefits
Capacity Planning
Troubleshooting
Determine Usage
ex. Peaks, Spikes, etc.
Advantages for MOSS
R
Determine heavily utilized
content database or sites
Examine usage patterns across
a 24 period when your not
monitoring the database directly
Capacity planning for moving
sites into new site collections
Central Management
New Feature in SQL Server
2008 to centrally manage
registered servers and
groups of servers
New Query
Execute queries against a
single registered server or a
group of servers
Ability to run TSQL against
all SQL Server instances
Evaluate Policies
Works with new policy-based
management to check
policies
R
Central Management
Great for managing MOSS installations that span more
than one SQL Server instance or MOSS databases that
reside in shared SQL Server environments
Example: SELECT @@VERSION AS ‘SQL Server Version’
R
Policy-based Management
Policy-based management framework for the
SQL Server Database Engine
Ensure compliance with policies for system
configuration
Implement and enforce best practices
Prevent/monitor changes to the system by
authoring policies for the desired configuration
Scale management across multiple servers
Reduce Total Cost of Ownership by simplifying
administration tasks
R
Evaluating Policy
On Demand (this is the default)
Evaluated when the user right clicks on the policy and
selects Evaluate from the menu.
On Schedule (SQL 2008 only)
Takes advantage of SQL Agent to check the policy on
a scheduled basis
On Change - Log Only (SQL 2008 only)
Evaluates a policy when a change is made and alerts
administrators when there is a policy failure
On Change – Prevent (SQL 2008 only)
Uses DDL triggers to prevent policy violations
R
Policy-based Management Example
MOSS - Best Practices for Capacity Management
http://technet.microsoft.com/en-us/library/dd335963.aspx
Best Practice of maximum of 5TB per SQL Server
instance and 100GB per Content database
Create a policy to check the size of each content
database
Create another policy to check the size of all content
databases on an entire SQL Server instance
On SQL 2008, schedule the policy to be checked
periodically
On SQL 2000/2005, check the policy on demand using
the Central Management capabilities of SQL Server 2008
NOTE: Can be combined with Windows PowerShell to run on-demand policy on a scheduled basis
R
DEMONSTRATION
USING SQL SERVER 2008
POLICY
R
Additional Resources
See our blogs for:
Recap of this session
Links to relevant white papers and walkthroughs
Download this slide deck
Bob German’s Blog
http://blogs.msdn.com/BobGerman
Rich Crane’s Blog
http://blogs.msdn.com/Rich_Crane
B
© 2007 Microsoft Corporation. All rights reserved.
This presentation is for informational purposes only. Microsoft makes no warranties, express or implied, in this summary.
25