<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Content Database on Matt Thornton</title>
    <link>https://matt-thornton.net/tags/content-database/</link>
    <description>Recent content in Content Database on Matt Thornton</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Tue, 28 Nov 2017 19:16:46 +0000</lastBuildDate><atom:link href="https://matt-thornton.net/tags/content-database/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>SharePoint 2010 pain - splitting a large content database</title>
      <link>https://matt-thornton.net/tech/powershell-tech/sharepoint-2010-pain-splitting-large-content-database/</link>
      <pubDate>Tue, 28 Nov 2017 19:16:46 +0000</pubDate>
      
      <guid>https://matt-thornton.net/tech/powershell-tech/sharepoint-2010-pain-splitting-large-content-database/</guid>
      
        <description>&lt;p&gt;I know, I know. SharePoint 2010. Bad. But here I am.&lt;/p&gt;
&lt;p&gt;Much of the pain I have been going through over the last week or so is frankly caused by the biggest mistake that a someone designing a new SharePoint environment can make: not planning for data volumes. It doesn&amp;rsquo;t matter how many times your client tells you “ah, it&amp;rsquo;ll never grow that big, we won&amp;rsquo;t use it much” - ignore them, they are lying.&lt;/p&gt;</description>
      
    </item>
    
  </channel>
</rss>