Sharepoint Content DB size
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
Who is Participating?
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 ...
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
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