Caracteristicas de estudio de SQL Server 2008 y MOSS Ing. Eduardo Castro Martinez, PhD Microsoft SQL Server MVP http://ecastrom.blogspot.com http://comunidadwindows.org

1. MOSS 2007 and SQL 2008A must! Ing. Eduardo Castro, PhD ecastro@mswindowscr.orgComunidad Windows

2. 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

3. Step by Step Guide http://andreasglaser.net/post/2008/08/14/Installing-MOSS-2007-on-Windows-Server-2008-and-SQL-Server-2008-Part-1-Overview.aspx

4. 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

5. 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.

6. Site Collections and Content Databases

7. Content Database Example Company Portal Document Repository Team Sites http://knowledge http://team Dept. Portals Central AdminSite SSP AdminSite http://portal http://someserver:40203 http://someserver:31415 My Sites Web application Content DB Site Collection http://my

8. 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

9. Compressed By Default One checkboxturns oncompressionfor allbackups – evenfrom SharePointCentral Admin!

10. Backup Compression Example Content database with ~370K documents 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 (test corpus was 360,000 text files)

11. DEMONSTRATION Compressing SharepointBackups

12. MOSS High Availability Load Balancing Web Web Web Web Web Web Application MOSS with SQLClustering SQL SQL Load Balancing Web Web Web Web Web Web MOSS with SQLMirroring or LogShipping Application SQL SQL Mirroring orLog Shipping

13. 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 Web Web Web

14. 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 Up To 73% Compression 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

15. 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 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 Web Web Web Web

16. 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

17. 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

18. PerformanceStudio Benefits Capacity Planning Troubleshooting Determine Usage ex. Peaks, Spikes, etc. Advantages for MOSS 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

19. 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

20. 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’

21. 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

22. 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

23. 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

24. DEMONSTRATION Using SQL Server 2008 Policy

25. Additional Resources See our blogs for: http://comunidadwindows.org Eduardo Castro Bloghttp://ecastrom.blogspot.com http://andreasglaser.net/post/2008/08/14/Installing-MOSS-2007-on-Windows-Server-2008-and-SQL-Server-2008-Part-1-Overview.aspx http://blogs.msdn.com/bobgerman/archive/2009/04/07/moss-2007-and-sql-server-2008-better-together.aspx

26. http://comunidadwindows.org 26