8. SQL Server Configuration Deciding on the SQL Cluster Configuration Number of nodes in the Cluster Number of instances in the cluster Deciding drives per instance and drive size
9. SQL Server Configuration - Example Total data size = 1 TB 2 nodes in the Cluster Number of instances in the cluster = 1 Deciding drives per instance and drive size Drives: C: = OS D: = 250 GB (Data) E: = 250 GB (Data) F: = 250 GB (Data) G: = 250 GB (Data) H: = 500 GB (Log) I: = 1 TB (Backup) Drives: C: = OS D: = 500 GB (Data) E: = 500GB (Data) F: = 500 GB (Log) G: = 1 TB (Backup) Drives: C: = OS D: = 1 TB (Data) E: = 500 GB (Log) F: = 1 TB (Backup)
28. Questions? Thank you & best regards Nilesh Mehta NGenious Solutions, Inc. 1075 Easton Ave., Tower1, Suite #6 Somerset, NJ 08873 Ph: (732) 873-3385 Cell: (201) 230-7922 Fax: (413) 803-8749 E-mail: [email_address] URL: www.ngenioussolutions.com
Notas do Editor
Talk about our current environment issues – Number of sites in 2007 vs. sites in 2008, Data size, about having to clean up disk space weekly, shrink database, having to move sites from one database to another. Downtime for end users while we perform maintenance.
Collaboration Sites - # Team sites with regular site quota – Possibly in the 1000’s Portal Sites - Sites with Host Header URL or Large Content Size – Possibly about 25+ sites Application Sites - Custom Applications built on SharePoint or Dedicated web applications for specific client requirements
SQL Cluster Configuration – Deciding on the Server Hardware, Number of CPU’s, Memory, OS – 32-bit vs. 64-bit, Number of drives, Drive sizes, Number of nodes in the cluster, Active / Passive vs. Active / Active
Microsoft states keep content db’s around 25-30 GB. How real world is that? If you environment grows up to 1500 Sites at 1 GB / site, you can host about 25 – 30 sites per database. That means you will be hosting about 50 databases. When it comes to finding out which sites belonged to which content Database, you are going to have a really tough time finding that out. Especially if the site is deleted and needs to be restore, because SharePoint keeps no trace of the same, or if the site was moved from one DB to another and you need to restore a version from when it was in the original DB.
Talk about end user impact when you have to perform maintenance. Due to moving sites, corrupt sites? If you have more sites in the same database, when you bring it down you impact everyone. At less number of sites per content database, you can perform maintenance by impacting a smaller audience. Talk about pros and cons of setting really small site quota.
SQL Cluster Configuration – Deciding on the Server Hardware, Number of CPU’s, Memory, OS – 32-bit vs. 64-bit, Number of drives, Drive sizes, Number of nodes in the cluster, Active / Passive vs. Active / Active
CON: Only CON is you cannot select which database to restore site in. If you use CreateInDatabase argument, it creates a brand new database. NOTE: Do not delete large sites from Central administration. Often we have seen the Microsoft Wheel spinning when it tells us that it is doing something (and not showing verbose progress ) and then the process times out. With large sites, if the process times out, there are possibilities that it will leave corrupt sites behind.