locked
Reduce content database size RRS feed

  • Question

  • Using SharePoint 2007 and I have a content database of size 150GB. How can I reduce or manage its size?

    Right now there is only one site collection in the web application to which this content DB is attached to. But there are many document libraries and inside them many files. Is there a way to reduce or manage it?

    If I create a new content DB from CA, will it start saving files in this content DB or it will continue to use old content DB?

    Monday, November 3, 2014 10:06 AM

All replies

  • If you create a new content db, you can assign it to new site collections that will add content to the new db. Old site collections will continue to use the old content db.

    If you have a db that is too large (say 150 GB) but with enough space in it, you can trasnfer the site collection in a new content db that is smaller. In your case I believe your option is to migrate smaller pieces of content to separate site collections. I myself like to use 3rd party migration tools to do that (such as DocAve or Quest).


    Kind regards,
    Margriet Bruggeman

    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

    Monday, November 3, 2014 10:49 AM
  • If you create a new content db, you can assign it to new site collections that will add content to the new db. Old site collections will continue to use the old content db.

    If you have a db that is too large (say 150 GB) but with enough space in it, you can trasnfer the site collection in a new content db that is smaller. In your case I believe your option is to migrate smaller pieces of content to separate site collections. I myself like to use 3rd party migration tools to do that (such as DocAve or Quest).


    Kind regards,
    Margriet Bruggeman

    Lois & Clark IT Services
    web site: http://www.loisandclark.eu
    blog: http://www.sharepointdragons.com

    But how can I migrate smaller pieces of content to separate site collections because this content DB only have one site collection with many document libraries. If I move document libraries to different site collections then user won't be able to access it easily like they do now.

    By the way is there a way to check exactly which site or document library is taking the largest space in content DB?

    Monday, November 3, 2014 11:03 AM
  • Ok I ran a couple of queries to get the size of tables in SQL Server in my content DB and it is showing very less size. My content DB MDF file is 150GB+ but the actual space being used by tables is around 1GB.

    What's going on?

    Monday, November 3, 2014 11:11 AM