Oit2010 model databases
0 likes179 views
The document provides information on the various databases that support Microsoft SharePoint 2010 products, including their relative sizes, recommended co-location, scaling guidance, and recommended SQL Server editions. It includes a chart that defines each database's purpose and characteristics. The databases support features like search, user profiles, social tagging, usage analytics, and business data connectivity.
Oit2010 model databases
- 1. Databases That Support SharePoint 2010 Products Microsoft® SQL Server® databases are integral to Microsoft® SharePoint® 2010 Products. The databases used Relative size: Database size, relative to other SharePoint Scaling guidance: Scale up: to increase the size available to the Recommended SQL Server edition: A specific edition of SQL in a specific environment are determined by the product, version, edition, and features that are running. Database Definitions databases. (Not to scale) database, move to a larger server. Scale out: to increase the size available to the database, add another database. Multiple Server that is recommended, and why. In general, in this poster, recommendations are made based on the assumption that you are size, and the edition of SQL Server that you run will be determined by the capacity and feature requirements of your Co-location guidance: Whether a database must or must not be database icons indicate scale out. running an enterprise environment. environment. located on the same server instance with another database. Read/write characteristics: Whether the database is mostly used For more detailed information about each database, see the articles: for reading or writing data. · Database types and description for SharePoint Server 2010 (http://go.microsoft.com/fwlink/?LinkId=187312) · Database types and description for SharePoint Foundation 2010 (http://go.microsoft.com/fwlink/?LinkId=187313). Microsoft SharePoint Microsoft SharePoint Server 2010, Microsoft SharePoint Server 2010, SQL Server Foundation 2010 Standard edition Enterprise edition Configuration Search Administration Profile Word Automation Services PerformancePoint System v Contains data about all SharePoint databases, all v (Search service application) (User Profile service application) (Word Automation Services service application) (PerformancePoint service application) Internet Information Services (IIS) Web sites or Web Hosts the Search application configuration Stores and manages users and their social Stores information about pending and completed Stores temporary objects and persisted user applications, trusted solutions, Web Part packages, and access control list (ACL) for the crawl information. document conversions. comments and settings. master site templates, and Web application and farm settings component. Relative size: Medium-large Relative size: Small Relative size: Small Records all system level information for a SQL Server specific to SharePoint 2010 Products, such as default Relative size: Medium Co-location guidance: None Co-location guidance: None Co-location guidance: None instance, including logins, configurations, and other quota and blocked file types. Co-location guidance: None Scaling guidance: Scale up the database Scaling guidance: Scale up the database that Scaling guidance: Scale up the database that databases. Relative size: Small Scaling guidance: Scale up the database that supports the service application supports the service application instance. supports the service application instance. You can Relative size: Small Co-location guidance: Must be co-located with that supports the service application instance. (Significant growth is unlikely). scale out by creating additional instances of the Co-location guidance: None Central Administration content database instance. You can scale out by creating additional service application, however, the decision to create Scaling guidance: Scale up. (Significant growth is unlikely). Scaling guidance: Scale up—only one configuration You can scale out by creating additional instances of the service application, a separate service application is likely to be based database is supported per farm. (Significant growth is instances of the service application, however, the decision to create a separate on business, rather than scale, requirements. unlikely). however, the decision to create a separate service application is likely to be based on Read/write characteristics: Read-heavy service application is likely to be based on business, rather than scale, requirements. business, rather than scale, requirements. Read/write characteristics: Read-heavy msdb Records operators, and used by SQL Server Agent to Central Administration Content schedule alerts and jobs. v Content database for the Central Administration site. Crawl Synchronization Relative size: Small Co-location guidance: None Relative size: Small Co-location guidance: Must be co-located with (Search service application) (User Profile service application) Scaling guidance: Scale up. (Significant growth is unlikely). configuration database Stores the state of the crawled data and the Stores configuration and staging data for Scaling guidance: Scale up—only one Central Administration content database is supported per crawl history. Relative size: Extra-large Co-location guidance: In large-scale use when profile data is being synchronized with directory services such as Active Directory. Related Products farm. (Significant growth is unlikely). environments, locate on a server that does Relative size: Medium-large, determined model not contain the Property database. by number of users, groups, and the ratio of Used as the template for all databases created in an Content Scaling guidance: Scale out—add more users to groups The following products must be installed in a farm that is running SharePoint Server 2010 Enterprise Edition. instance. Stores all site content, including site documents or v Crawl databases. Read/write characteristics: Read-heavy Co-location guidance: None Relative size: Small Co-location guidance: None files in document libraries, list data, Web part Scaling guidance: Scale up the database Recommended SQL Server edition: that supports the service application v properties, audit logs, sandboxed solutions, and user names and rights. All of the data for a specific site SQL Server 2008 Enterprise edition, so that the Search service application can take instance. Microsoft Project Server 2010 Microsoft FAST Search Server Scaling guidance: Scale up. (Significant growth is unlikely). resides in one content database. Content databases You can scale out by creating additional 2010 for SharePoint advantage of data compression. instances of the service application, can contain more than one site collection. Also stores data for Office Web Applications, if in use. however, the decision to create a separate tempdb Relative size: Varies based on number and size of service application is likely to be based on Holds all temporary tables and temporary stored procedures documents and number of users. Property business, rather than scale, requirements. and fills any other temporary storage needs. The tempdb Important: We strongly recommended limiting the size (Search service application) Read/write characteristics: Even Draft Search Administration database is re-created every time the SQL Server instance is of content databases to 200 GB to help ensure Stores information associated with the Contains data for editing projects and tables Stores and manages search setting groups, started. system performance. crawled data, including properties, history, used by the Project Queue. Data in this keywords, synonyms, document and site Relative size: Medium, depending on activity Content database sizes up to 1 terabyte are and crawl queues. Social Tagging database is not directly accessible by end promotions and demotions, term entity Co-location guidance: Locate on a separate spindle from all supported only for large, single-site repositories and Relative size: Large to extra-large (User Profile service application and the users. extractor inclusions and exclusions, spell other databases archives with non-collaborative I/O and usage patterns, such as Records Centers. v Co-location guidance: In large-scale environments, put this database on its own Metadata Management service application, if tags are used for Relative size: Medium Co-location guidance: Must be located on check exclusions, best bets, visual best bets, and search schema metadata. Scaling guidance: Scale up Co-location guidance: None server to achieve faster query results. metadata) the same database instance as the Archive Relative size: Small Scaling guidance: Scale up a database that Scaling guidance: Scale out—add more Stores social tags and notes created by and Published databases Co-location guidance: None supports a site collection. Scale out at the Web Property databases. users along with their respective URLs. Scaling guidance: Scale up. Scaling guidance: Scale up. (Significant application level: add more content databases as Read/write characteristics: Write-heavy Relative size: Small to extra large, growth is unlikely.) needed to support additional site collections. Recommended SQL Server edition: SQL Server 2008 Enterprise edition, so that determined by the number of tags and ratings created and used Read/write characteristics: Read-heavy Microsoft SQL Server Usage the Search service application can take advantage of data compression. Co-location guidance: None Scaling guidance: Scale up the database Published Reporting Services that supports the service application Contains a copy of all of the projects that (Usage and Health Data Collection service have been published, tables specific to application) Stores health monitoring and usage data instance. You can scale out by creating additional Project Server (timesheets, resources, Microsoft SQL Server SQL Server Reporting Services is often used with SharePoint custom fields, security definitions, and other v temporarily, and can be used for reporting and diagnostics. instances of the service application, however, the decision to create a separate metadata), and the tables used by the PowerPivot for SharePoint Server 2010 Access Services, Excel Services, PerformancePoint Services, and Visio Services, but is not service application is likely to be based on Timesheet Queue. Data in this database is The Usage database is the only SharePoint required. business, rather than scale, requirements. not directly accessible by end users. database that be queried directly and have Relative size: Large schema modified by external applications. Web Analytics Reporting Read/write characteristics: Read-heavy Relative size: Extra-large. Size varies based on (Web Analytics service application) Co-location guidance: Must be located on PowerPivot Service Application the same database instance as the Archive Stores the location of cached or loaded PowerPivot ReportServer retention policy. Stores aggregated standard report tables, and Draft databases. data files, data refresh schedules, and PowerPivot Co-location guidance: Place on separate spindle fact data aggregated by groups of sites, date, Stores all report metadata including report definitions, report Scaling guidance: Scale up. usage data that is copied from the central usage data Scaling guidance: Scale up the database. Only and asset metadata, and diagnostics history and snapshots, and scheduling information. When one Usage and Health Data Collection service v information. collection database. PowerPivot requires SQL Server 2008 R2 Enterprise ReportServer is in use, report documents are stored in application instance is supported per farm. Relative size: Extra-large to enormous. Size Managed Metadata Service Edition Analysis Services in the environment. SharePoint content databases. Read/write characteristics: Write-heavy varies based on retention policy. (Managed Metadata service application) Archive Relative size: Small Co-location guidance: None Stores managed metadata and syndicated Co-location guidance: Must be located on the same Stores the backup data of projects, Relative size: Small Scaling guidance: Scale up the database content types. database server as the ReportServerTempDb database. resources, calendars, enterprise custom Co-location guidance: None that supports the service application instance. Relative size: Medium Supports service applications: Often used with Access Business Data Connectivity fields, the enterprise global Project Web Scaling guidance: Scale up. (Significant growth is services, Excel services, PerformancePoint services, and v Recommended SQL Server edition: Co-location guidance: None (Business Data Connectivity service Access view definitions, Project Web Access unlikely). SQL Server 2008 Enterprise edition, so that Scaling guidance: Scale up the database Visio services, but not required. application) system settings, and category and group Additional information: When in use, PowerPivot the Web Analytics service application can that supports the service application instance. Scaling guidance: Scale up Stores external content types and related objects. security settings. Data in this database is not stores additional data in content databases and in the take advantage of table partitioning. Add additional instances of the Managed Read/write characteristics: Read-heavy Relative size: Small directly accessible by end users. Central Administration content database. PowerPivot- Metadata service application to scale out, or Relative size: Small, but can grow to extra- related files are often quite large. Co-location guidance: None for business reasons. large if in use. Growth limits can be set. Scaling guidance: Scale up. (Significant growth Read/write characteristics: Read-heavy Co-location guidance: Must be on the same is unlikely). Web Analytics Staging database instance as the Published and Draft ReportServerTempDB Read/write characteristics: Read-heavy (Web Analytics service application) Stores all of the temporary snapshots while reports are databases. Temporarily stores un-aggregated fact data, running. Scaling guidance: Scale up. Relative size: Varies frequently. Small to extra-large, Application Registry v asset metadata, and queued batch data. Relative size: Medium, determined by the depending on use of cached report snapshots. v (Application Registry service application) number of reports generated. Co-location guidance: Must be located on the same database server as the ReportServer database. Stores data required for backward compatibility for Co-location guidance: None Reporting the Business Data Connectivity API. Used during Scaling guidance: Scale out—add another Scaling guidance: Scale up Repository for the entire portfolio of projects, upgrade, and can be deleted when upgrade is Web Analytics Staging database. Secure Store Read/write characteristics: Read-heavy complete. Relative size: Small v (Secure Store service application) including stable snapshots of each project plan based on the last time a project was Stores and maps credentials such as account published, and de-normalized time-phased Co-location guidance: None names and passwords. data. Data in the Reporting database is Scaling guidance: Scale up. (Significant growth Relative size: Small accessible by end users. is unlikely). Co-location guidance: For secure credential Legend Relative size: Large Read/write characteristics: Read-heavy storage, it is recommended that the secure Co-location guidance: Can be on different State store database be hosted on a separate SQL Server instance than other Project (State service application, InfoPath Forms database instance with access limited to one Server 2010 databases. Subscription Settings Services, Visio Services) administrator. Scaling guidance: Scale up. Database size ranges Other notations (Microsoft SharePoint Foundation v Stores temporary state information for InfoPath Forms Services, Exchange, the Scaling guidance: Scale up the database that supports the service application instance. Read/write characteristics: Read-heavy (not to scale) Subscription Settings service) chart Web Part, and Visio Services. You can scale out by creating additional Stores features and settings information for hosted Relative size: Medium-large, depending on instances of the service application, however, Small: Installed with Microsoft Search Server 2010 customers. This database is not created by default—it must be created by using Windows PowerShell or usage of features that store data in it. Co-location guidance: None the decision to create a separate service application is likely to be based on business, 1 GB or less v Express and Standard SQL Server. Scaling guidance: Scale out—add another rather than scale, requirements. Relative size: Small State database by using Windows Medium: Co-location guidance: None PowerShell cmdlets. Up to 100 GB Scaling guidance: Scale up the database that Read/write characteristics: Slightly read- supports the service application instance. heavy. You can scale out by creating additional instances of Large: Supports multiple the service application, however, the decision to Up to 1 databases (scales out) create a separate service application is likely to be terabyte based on business, rather than scale, requirements. Read/write characteristics: Read-heavy Extra-large: 1 terabyte or more © 2010 Microsoft Corporation. All rights reserved. To send feedback about this documentation, please write to us at [email protected].