This webinar discusses:
-Common barriers companies experience when moving to the cloud
-How SD-WAN changes the way we look at networks
-Best practices customers should employ moving forward with cloud migration
-What happens behind the scenes of SteelConnect’s one-click button
Course Of The Month
Become a Premium Member and unlock a new, free course in leading technologies each month.
Solved
Sharepoint Content DB size
Posted on 2014-12-15
Hi Experts
I need to know how can I resolve big content DB issue suppose it’s around 300 GB .
1- Can I add another content DB to my site? I guess not
2- Should I use partitioning on SQL
thanks
I need to know how can I resolve big content DB issue suppose it’s around 300 GB .
1- Can I add another content DB to my site? I guess not
2- Should I use partitioning on SQL
thanks
[X]
Welcome to Experts Exchange
Add your voice to the tech community where 5M+ people just like you are talking about what matters.
- Help others & share knowledge
- Earn cash & points
- Learn & ask questions
2-
2
6 Comments
Yes you can add another content database to the site by turning your current content db offline and create a new one though central admin > manage content database. All your new sites would get provisioned on new db till the time your existing database is offline.
Thanks Mohit
Yes you are right.the problem is the users are storing the documents in the first site and I can not create new site and ask them to store the data in new one.
I don't want to create new site.
Yes you are right.the problem is the users are storing the documents in the first site and I can not create new site and ask them to store the data in new one.
I don't want to create new site.
In that case, you may have to move the site to the new content database. Follow this article to move it via powershell
http://technet.microsoft.com/en-us/library/ff607915(v=office.15).aspx
http://technet.microsoft.com/en-us/library/ff607915(v=office.15).aspx
But again I have a big growing Content DB . the point is if I can spilit it in to two database or ...
If you are using a document centre/records centre then 300GB if is fine.
Although MS recommend a 200GB limit for Content DBs on other Sharepoint uses, It's just a recommendation - I've had much bigger content DBs on a 2007 team site and it worked fine, for example. Talking to other professionals they have agreed that this seems to be quite low limit because Sharepoint is so configurable/developable and MS do not want to become liable for people "over using" it. If you are runing an OOTB config it is much safer to use a big content db, but if you are using lots of customised software/workflows etc you should look to do something about it.
If you really need to split up your content DB, then you have to look at your whole architecture/topology, because you are going to have to split your data across web applications, which means separate site collections. This could be a big job, or it may be as simple as a creating the new topology and and running a few powershell commands to transfer the data - it really depends on your current system and what you want to do with - so it is impossible to answer in this format, it needs proper consutancy and planning since you could be doing anything with your system that renders my advice here nonsensical :)
I would suggest you start by building a document centre/records centre to act as your central archive, and look to start transfering the "system wide" information into that from it's current location.
At the very least I would plan that any new teams/departments/organisa
Check the best practise limits (2013, but don't think they have changed much):
http://technet.microsoft.com/en-us/library/cc262787%28v=office.15%29.aspx#ContentDB
Although MS recommend a 200GB limit for Content DBs on other Sharepoint uses, It's just a recommendation - I've had much bigger content DBs on a 2007 team site and it worked fine, for example. Talking to other professionals they have agreed that this seems to be quite low limit because Sharepoint is so configurable/developable and MS do not want to become liable for people "over using" it. If you are runing an OOTB config it is much safer to use a big content db, but if you are using lots of customised software/workflows etc you should look to do something about it.
If you really need to split up your content DB, then you have to look at your whole architecture/topology, because you are going to have to split your data across web applications, which means separate site collections. This could be a big job, or it may be as simple as a creating the new topology and and running a few powershell commands to transfer the data - it really depends on your current system and what you want to do with - so it is impossible to answer in this format, it needs proper consutancy and planning since you could be doing anything with your system that renders my advice here nonsensical :)
I would suggest you start by building a document centre/records centre to act as your central archive, and look to start transfering the "system wide" information into that from it's current location.
At the very least I would plan that any new teams/departments/organisa
Check the best practise limits (2013, but don't think they have changed much):
http://technet.microsoft.com/en-us/library/cc262787%28v=office.15%29.aspx#ContentDB
Featured Post
Question has a verified solution.
If you are experiencing a similar issue, please ask a related question
This post looks at MongoDB and MySQL, and covers high-level MongoDB strengths, weaknesses, features, and uses from the perspective of an SQL user.
- Query Syntax
- SQL
- Databases
- MySQL Server
- MongoDB
- NoSQL Databases, Percona
In this blog post, we’ll look at how ClickHouse performs in a general analytical workload using the star schema benchmark test.
The viewer will learn how to simulate a series of coin tosses with the rand() function and learn how to make these “tosses” depend on a predetermined probability.
Flipping Coins in Excel: Enter =RAND() into cell A2:
Recalculate the random variable…
Viewers will learn how to use the SELECT statement in SQL and will be exposed to the many uses the SELECT statement has.
Suggested Courses
Earn Certification
HTML5 Specialist - Certification
Free withPremium
Course of the Month7 days, 1 hour left to enroll
Earn Certification
MCSA Configuring Windows 7 Exam 70-680
$49.00$44.10
622 members asked questions and received personalized solutions in the past 7 days.
Join the community of 500,000 technology professionals and ask your questions.