内容数据库成长为大型 [英] Content DB Grown To Large

问题描述

问候所有

首先，我有IT经验，但对SharePoint来说绝对是全新的.我被要求负责管理我们的SP2010安装.我的首要任务是处理我们收到的Content DB to Large消息.

First a little background, I have IT experience but am absolutely brand new to SharePoint. I have been asked to take up administering our SP2010 installation. My first task is to handle the Content DB to Large messages we have received.

我已经进行了许多搜索，并且看到了许多解决方案和建议.

I've done a number of searches and have seen a multitude of solutions and suggestions.

我正在寻找最佳实践，流程效率以及一种可以使我尽可能免除头痛的方法.我已经在我的SharePoint数据库上执行了收缩"操作，这对内容数据库的大小确实有所帮助， 但是此文件很快就会再次增长(缩小后我还不到100个演出).

I'm looking for best practices, efficiency of the process, and a methodology that will leave me as headache free as possible. I have already performed 'Shrink' operations on my SharePoint databases, which did help the Content DB as far as it's size goes, but this file will soon be growing again (I'm just under 100 gig after shrinking).

据我了解，我要创建一个供内容数据库使用的新数据库，然后将当前的内容数据库移至新"内容数据库.虽然我想就是这个过程，但是整个Content DB问题对我来说还是有点模糊.

From what I understand I'm to create a new database for use by the Content DB then move the current Content DB to the 'New' Content DB. while I guess that's the process, this whole Content DB issue is a little foggy to me.

预先感谢您提供此问题的帮助.

Thank you in advance for your help with this issue.

推荐答案

您的备份/还原过程是什么样的? "100GB限制"是SharePoint的产物，即使在2010年也不再适用.例如，1TB +的内容数据库并非没有道理.

What does your backup/restore process look like? The '100GB limit' is an artifact of SharePoint and no longer applies, even to 2010. 1TB+ content databases aren't unreasonable, for example.

大型"内容数据库通常需要注意两个问题:

Generally there are two issues to be aware of with 'large' content databases:

1)您的备份和还原过程需要多长时间?是否在可接受的业务/运营范围内?通常，在处理大型数据库时，您只想使用基于SQL的备份，而不是基于SharePoint的备份.

1) How long does your backup and restore process take? Is it within acceptable business/operational limits? In general, when dealing with large databases, you only want to use SQL-based backups, not SharePoint-based backups.

2)存储内容数据库的MDF/LDF的基础磁盘子系统的性能如何?如果您要使用1TB以上的存储空间，则指导原则是最低0.25 IOPS/GB，建议2 IOPS/GB.

2) What is the performance of the underlying disk subsystem where the MDF/LDF of the content database is stored? If you're going 1TB+, the guideline is 0.25 IOPS/GB minimum, 2 IOPS/GB recommended.

最后，缩小数据库不是一个好习惯，除非您要释放50％以上的基础磁盘空间.尽管SharePoint最终会通过内部运行状况分析器作业重建内部索引，但它会破坏内部索引.

Lastly, shrinking databases isn't good practice unless you're freeing 50%+ of underlying disk space. It destroys the internal indexes, although SharePoint will rebuild them via an internal health analyzer job eventually.

这篇关于内容数据库成长为大型的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！