Successfully reported this slideshow.

Sql Server 2008 And Moss

2,050 views

Published on

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

Published in: Technology
  • Be the first to comment

Sql Server 2008 And Moss

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

×