1 / 8

SQL Cluster Administration and Database Organization Workshop Agenda

This workshop agenda covers Database Organization, SQL Cluster Administration, and management of various databases and services including SharePoint databases. It discusses reasons to change DB organization, splitting databases, cluster administration, and supervision of SQL Server instances. It also addresses content databases, log files, and the allocation of databases for different functions.

rosina
Télécharger la présentation

SQL Cluster Administration and Database Organization Workshop Agenda

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Databases Workshop

  2. Agenda • DatabaseOrganization • SQL Cluster Administration WAT - Atelier "Sites Distants" - Cadrage des tests

  3. CURRENT DB Organization : 20 DB on 4 SQL Server inst. • SharePoint Databases • SessionStateService (L01) • StateService (L01) • WAT_CONFIG (L01) • WAT_SVC_UserProfileService_Profiles (L01) • WAT_SVC_UserProfileService_Social (L01) • WAT_SVC_UserProfileService_Sync (L01) • WAT_SVC_SearchService (L01) • WAT_SVC_SearchService_AnalyticsReportingStore (L03) • WAT_SVC_SearchService_CrawlStore (L03) • WAT_SVC_SearchService_LinksStore (L03) • WAT_SVC_MetaDataService (L04) • WSS_UsageApplication (L01) • Content Databases • WAT_CONTENT_CentralAdmin (L01) • WAT_CONTENT_Common (L01) • WAT_CONTENT_CommunitySites1 (L01) • WAT_CONTENT_Content_site (L01) • WAT_CONTENT_Personal_Sites1 (L01) • WAT_CONTENT_THEMATICS (L02) • OtherDatabases • AIGImport (L01) • CacheDb (L02) WAT - Atelier "Sites Distants" - Cadrage des tests

  4. Reasons to change DB Organization • The content databases are expected to grow as the number of userspicks up • The MS recommandation is to keep DB sizesunder 400 GB • This leads us to split DB. WAT - Atelier "Sites Distants" - Cadrage des tests

  5. Splitting the databases • Editorial Content • Currently : WAT_CONTENT_Common, WAT_CONTENT_site, WAT_CONTENT_THEMATICS • Planned : 9 databases • Personal Sites • Currently : WAT_CONTENT_Personal_sites_1 • Planned : 120K user profiles, max number of sites per base = 10KIn the run, the personal sites must use 12 DBs. • Community Sites • Currently : WAT_CONTENT_Community_sites1 • Planned : average size of a community site = 5 GB, 80 communities per DBExpectednumber of communities = 5000, Nb of DB = 70These DB canbeprovisionnedprogressively WAT - Atelier "Sites Distants" - Cadrage des tests

  6. SQL Cluster Administration • Database log files sizes • Supervision • Maintaining SQL Server instances on theirpreferrednode WAT - Atelier "Sites Distants" - Cadrage des tests

  7. CONTENT DATABASES LOG FILES • The content databases are saved by DPM • DPM isexpected to truncate and shrink the log files • For somereason, log files are not handled as expected. • It mightbenecessary to truncate and shrinkmanually • The DB SessionStateServicegrowswith no limit • The issue isunder investigation by Microsoft Premier • Loggingparameters must beadjusted for some of the other DB • Who has the responsibility to makethese changes ? • The growth of files beyondlimitsdoes not trigger alerts • Which supervision is in charge ? WAT - Atelier "Sites Distants" - Cadrage des tests

  8. Instances and Nodes • The SQL cluster is made of 6 physicalnodes • E01, E02, E03 (Saint-Denis) • E04, E05, E06 (Clichy) • When running in the standard mode: • L01, L03, L04 run on node E03 • L02 run on node E01 • In case of the loss of a physical server, the instances are moved to the nextavailablenode in theirpreferencelist. • At reboot of theirnode, instances are moved, but theirshould return to theirpreferrednodeafterrebbotiscomplete. WAT - Atelier "Sites Distants" - Cadrage des tests

More Related