MOSS 2007 and SQL 2008: Better Together Rich Crane and Bob German Microsoft Technology Center |...
-
Upload
carmel-underwood -
Category
Documents
-
view
222 -
download
2
Transcript of MOSS 2007 and SQL 2008: Better Together Rich Crane and Bob German Microsoft Technology Center |...
MOSS 2007 and SQL 2008:
Better Together
Rich Crane and Bob GermanMicrosoft Technology Center | Boston
AgendaMOSS Database ReviewNew 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 benefitOffice SharePoint Server 2007 (Standard or Enterprise)Windows SharePoint Services 3.0
You need SP1 to make it work!Existing install: Upgrade to SP1Clean install: Download SharePoint w/SP1 slipstream
B
SharePoint Databases
Configuration – One per farm, stores information about the farm topology and settingsContent – Stores all content; it is usual to have several content databasesWSS Search – Property store for WSS searchSSP Search – Displayable document properties/metadata for MOSS SearchSingle Sign-On – SSO credential mappingsSSP – Other Shared Services such as user profiles, audiences, etc.B
Site Collections and Content Databases Farm
Web Application
Content DB
Site Collection
Top Level Site
Site
Site
Site Collection
Top Level Site
Site
Site
Content DB
Site Collection
Top Level Site
Web Application
Content DB
Site Collection
Top Level Site
Site Collection
Top Level Site
Site
Site
Site
Site Collection
Top Level Site
B
Content Database Example
Company Portal
Central AdminSite
SSP AdminSite
Dept. Portals
Document Repository
http://portal
http://my
http://teamhttp://knowledge
http://someserver:40203
http://someserver:31415
Team Sites
My SitesWeb applicationContent DBSite CollectionB
Database Backups & MOSSDatabase Backups are a large part of
backing up SharePointThey’re not everything … still need to address:
Filesystem:Installed featuresServer configuration, IIS MetabaseSearch index
Granular RestoresRecycle bin helpsData Protection Manager 20073rd 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 checkboxturns oncompressionfor allbackups – evenfrom SharePointCentral Admin!
B
Backup Compression ExampleContent database with ~370K
documentsTest 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,314SQL 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
(test corpus was 360,000 text files)B
MOSS High Availability
MOSS with SQLClustering
MOSS with SQLMirroring or LogShipping
Web Web
Load Balancing
SQL SQL
Application
WebWebWebWeb
Mirroring orLog Shipping Web Web
Load Balancing
SQL SQL
Application
WebWebWebWeb
B
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 improveService Level Agreements(SLA) by reducingdown time
Web WebWebWeb
R
Database MirroringPopular HA/DR solution that offers zero-to-minimal data-loss for your MOSS database environment
Out-Of-The-Box withSQL Server 2008 STD/EE
R
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)
Can reduce network utilization or improve Service Level Agreement (SLA) depending on transaction patterns
Up To 73% Compression
Failover ClusteringRolling upgrade/patch support for SQL Server failover clusters to minimize downtime
Improve failover cluster setup reliabilityIntegrated OS cluster health checksIntegrated SQL Server setup health checks
Leverage new setup architectureEnable for sysprep and slip-streamDistributed setup on each node – No remote execution
Align with Windows Server 2008 features16-node failover clusters with SQL 2008 EEMore nodes are perfect for shared DB environmentsIPV6 and DHCP supportHeterogeneous hardware and iSCSI supportNot aligned with OR dependencies
Web
WebWeb
Web
R
Transparent Data Encryption (TDE)New Feature In SQL 2008
Transparently encrypts entire databaseEncrypt all data seamlesslyThis includes backups, transaction logs, and tempdbEasy to ImplementNo programming changes required to implementLow impact (~3-5% CPU) and can be much lower if most of the data is stored in memory
Easy to implement with MOSSRecommended to implement at a Content databaseAll Sites within Site Collections are protectedNo changes to MOSS (i.e. transparent)Consider moving sites which need encryption to their own SQL Server instance for performance
R
Performance StudioNew Feature in SQL Server 2008 for Performance Management (i.e. monitoring and troubleshooting)SQL Server Performance Dashboard based on system collection sets reports
Sever ActivityHigh level SQL Server and system informationShould be turned on all the timeLow overhead (that is, <5 percent)
Query StatisticsDetailed SQL Server informationDrill 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
PerformanceStudio
BenefitsCapacity PlanningTroubleshootingDetermine Usageex. Peaks, Spikes, etc.
Advantages for MOSSDetermine heavily utilized content database or sitesExamine usage patterns across a 24 period when your not monitoring the database directlyCapacity planning for moving sites into new site collections
R
Central Management
New Feature in SQL Server 2008 to centrally manage registered servers and groups of serversNew Query
Execute queries against a single registered server or a group of serversAbility to run TSQL against all SQL Server instances
Evaluate PoliciesWorks with new policy-based management to check policiesR
Central ManagementGreat 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 EngineEnsure compliance with policies for system configurationImplement and enforce best practicesPrevent/monitor changes to the system by authoring policies for the desired configurationScale management across multiple serversReduce 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 ExampleMOSS - 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 databaseCreate a policy to check the size of each content databaseCreate another policy to check the size of all content databases on an entire SQL Server instanceOn SQL 2008, schedule the policy to be checked periodicallyOn SQL 2000/2005, check the policy on demand using the Central Management capabilities of SQL Server 2008NOTE: Can be combined with Windows PowerShell to run on-demand policy on a scheduled basis
R
Additional Resources
See our blogs for:Recap of this sessionLinks to relevant white papers and walk-throughsDownload this slide deck
Bob German’s Bloghttp://blogs.msdn.com/BobGermanRich Crane’s Bloghttp://blogs.msdn.com/Rich_Crane
B