SQL Server Reference Guide

Mar 28, 2003

␡

⎙ Print

< Back Page 282 of 365 Next >

This is the second in a series on SharePoint and SQL Server. In this part of the series, I’ll be building on the information I shared in the first article, so if you haven’t had a chance to look that over, take a moment to do that now.

In this tutorial I’ll dig a little deeper into the practical steps you need to take for working with your SharePoint databases, but I’ll assume that you have the information from the first article, so I won’t repeat the same conditions and caveats here. I’ll have plenty of other ones, though — because based on your needs, layout, and many other factors you’ll get the standard DBA answer: “It depends”. That’s OK — I’ll give you lots of references at the end of the series to go and learn more about each of those areas.

Planning for Scale

As I mentioned earlier, your biggest impact is in the planning phase of your SharePoint Farm. As a refresher, take a look at the parts of the SharePoint “Farm”:

Figure 1

We’ll use this as a discussion point for the planning phase. With this background, the first tool you and your team should investigate is at http://www.sharepointsqlmodeler.com/. This tool will help you select the Edition of SQL Server based on the features you require, and it’s the first decision where you have a big impact. Selecting the wrong Edition might limit everything from performance to safety and recovery features, so this is a good place to start.

Hardware

Your next decision is the hardware. I put this decision after the Edition, since each Edition can use different classes of hardware. Obviously you want the highest architecture you can afford for SharePoint SQL Servers. SharePoint servers deal with two factors — locking, and large inserts and deletes. This means the areas of hardware to focus on are memory and I/O (drives and storage), rather than massive amounts of CPU power or excessive networking capabilities. That doesn’t mean you should “starve” those other two resources, just be aware of where the pressure on the system is.

Note that you haven’t made your choices on how many servers yet — that will come in a moment. Also — I’m discussing the data servers — there are other server types in a SharePoint Farm. You can learn more about those here: http://technet.microsoft.com/en-us/library/cc288751(office.12).aspx

High-Availability and Disaster Recovery (HADR) Planning

Although I can’t cover all of the information for planning for HA and DR, You have many options. I normally propose the following layers of protection:

Hardware Redundancy
Backup and Restore Strategies
Clustering: http://technet.microsoft.com/en-us/library/dd207311(office.12).aspx
Database Mirroring: http://go.microsoft.com/fwlink/?LinkId=83725&clcid=0x409
Log-Shipping: http://technet.microsoft.com/en-us/library/dd890507(office.12).aspx

You do not have the option of SQL Server Replication for SharePoint databases. Yes, I’m sure you can find an article or two out there where people have done it, but you’re in an unsupported environment, and you’re taking even more performance hits when you do — this is typical of SharePoint system articles. There’s always someone out there that has discovered some way to get around the rules, but the unintended consequences always catch up with the work-arounds.

Planning the Databases

I listed all of the databases that SharePoint 2007 uses in the last article, but there are four primary types of those databases:

Configuration
Content
Shared Services Provider (SSP)
Search

The Configuration database makes a Farm, because it stores the locations, paths and so on to not only the other databases, but even other servers in the Farm. So essentially it’s like a “master” system database in SQL Server, or the Registry in Windows. It contains the configuration for everything else.

This database isn’t actually accessed as often as the other databases, but it should be backed up, maintained and so on just like the others — I’ll cover that more in the next couple of sections.

The real focus is on the Content databases. This is where the majority of information and activity is. Keeping them separate, sometimes even onto other servers, can be a good strategy. Keeping them separate helps you maintain, monitor and change the performance at a more granular level. Not only that, there is one other concern that you need to be aware of. It’s best if you keep each Content database below 100 GB in size. That can be quite the challenge, with users wanting to store larger and larger documents in a single site or web area.

This helps you understand where you should work with your SharePoint administration team carefully. They need to be aware of this limit, since they understand what actually creates a Content database. If they aren’t aware of that linkage, check my links at the end of this series to learn more, but an easy way to tell is when they create a new site or area in the SharePoint administration tool, tell them always to look for a field where they enter a database name. If that field exists, that will potentially be a new Content database. They need to help you think through how big that site might get, because splitting them up later is not a trivial task.

As I mentioned, you’ll face the most issues with locking in these Content databases, as users put data and documents in and pull them out. This is why even looking at simple scripts inside a live SharePoint system is exceptionally bad. Running external scripts or processes outside of SharePoint code takes even more locks, slowing the system down even further. This is also the reason even simple or seemingly obvious changes to a SharePoint database, like adding or removing an Index is not supported, and a bad idea. The SharePoint administrators, the users, and system operations change even the structure of the database in ways you can’t predict. So when you change a structure element such as a View or Index, you can bring the system to a crawl. And no one wants that.

So planning the Content database layouts is one of the most critical steps you can take. Not only in how many and where they live, but the growth options and settings you should configure. I’ll cover many of those in a moment, but you can learn more about the sizing aspect here: http://technet.microsoft.com/en-us/library/cc298801(office.12).aspx

Make sure you check out that link, in addition to the options I’ll mention next.

Database Configuration Options

There are certain configuration options and steps that you need to follow for optimum stability and performance for a SharePoint database.

Set the databases to have automatically created and automatically updated statistics. This will cause some further blocking, but the tradeoff for performance is worth the locking it might cause.

Turn off the “Auto Close” setting in database options. That’s a good idea normally anyway, but it’s essential here.

Before you install any SharePoint databases, ensure that you have learned about and set up “Instant File Initialization” — you can read more about that here: http://www.sqlskills.com/BLOGS/KIMBERLY/post/Instant-Initialization-What-Why-and-How.aspx

As far as security options go, install SharePoint with a domain account, as a local admin on each box. The accounts need the following rights in SQL Server, and may even need the sysadmin role. Of course, if it has that role, the rest of these are not necessary to set up individually. This isn’t something we data professionals like very much, which is why I recommend that the SharePoint database be on its own server or group of servers. I just don’t like other folks having that much control in my data systems. At a base, the account that runs SharePoint needs the following roles:

SQL Server Logins
SQL Security Admin
DBCreator

The Server Farm Account (domain\SAFarm) should be separate, and not used for setup. Use it for application pools in IIS. It also needs:

SQL Server Logins
Admin
DBCreators
DBO for all DB's

Use at least one account for all Web Applications, and always use a separate account for the "Central Admin" Web app. It also needs:

DBO for its Content Database
R/W for SSP Content Database
Read for Config DB
Read for the Central Admin WebApp DB

In the final article in this series I’ll show you how to monitor and maintain your SharePoint data layer, and I’ll give you lots of external links to more information on this topic.

< Back Page 282 of 365 Next >

🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Privacy Notice

Overview

Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security

Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children

This site is not directed to children under the age of 13.

Marketing

Pearson may send or direct marketing communications to users, provided that

Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
Such marketing is consistent with applicable law and Pearson's legal obligations.
Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out

Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

As required by law.
With the consent of the individual (or their parent, if the individual is a minor)
In response to a subpoena, court order or legal process, to the extent permitted or required by law
To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
To investigate or address actual or suspected fraud or other illegal activities
To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links

This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020

Email Address