Post reply

database get bigger

  • July 19, 2011 at 4:03 pm

    #254679

    We have a sharepoint database getting bigger quickly.

    Now it is about 11 gb.

    What should I do at this point?

    Should I create a new file or file group?

    Thanks

  • July 19, 2011 at 4:36 pm

    #1355215

    11Gb is not very big. If you want to create a new file, that is up to you. If you do, I would consider placing the new file on a different disk.

    Jason...AKA CirqueDeSQLeil
    _______________________________________________
    I have given a name to my pain...MCM SQL Server, MVP
    SQL RNNR
    Posting Performance Based Questions - Gail Shaw[/url]
    Learn Extended Events

  • July 19, 2011 at 4:52 pm

    #1355224

    As Jason says 11GB isn't very large.

    Could you give a bit more detail here? Like what is the growth rate? Are there any specific tables that are unusually large? Are you getting performance issues?

    I don't know Sharepoint, but my immediate thought is, is it doing auditing of user actions and if so is this being cleared on a regular basis?

    I wouldn't make changes unless you have a particular goal in mind, like splitting of activity to another disk group because of performance issues.

    Cheers

    Leo

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • July 19, 2011 at 6:08 pm

    #1355261

    Thanks,

    but sorry I provided wrong information.

    The database now is 116 gb, and it gorws 6 gb every week.

  • July 19, 2011 at 6:54 pm

    #1355269

    Is the 116 G all .mdf file, or do you have an .ldf growing big because there's no regular t-log backup ?

  • July 19, 2011 at 6:56 pm

    #1355270

    That's only mdf file. We do have transaction log backup too.

  • July 19, 2011 at 7:28 pm

    #1355279

    sqlfriends (7/19/2011)

    We have a sharepoint database getting bigger quickly.

    Now it is about 11 gb.

    Also what version of Sharepoint are you using?

    Leo

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • July 20, 2011 at 4:04 am

    #1355449

    SQLRNNR's advice of creating the new file on a different disk is very good. Considering that your database is growing 6 Gb per week (312Gb per year), you may want to create more files in different disks. The other way is try to solved by creating multiple content databases in SharePoint and not allowing the databases to grow beyond 100 GB, but that is up to you and it depends if your organization will allow that. Good luck!



    My blog

  • July 20, 2011 at 10:06 am

    #1355800

    Thanks, we are using MOSS 2007 sharepoint server.

    I guess Ignacio A. Salom Rangel 's idea about creating a new content database may be a good idea.

    I just concerned if the database get's bigger, if later move from one server to the other, because the size it will be harder. So far we don't find any performance issue.

  • July 20, 2011 at 3:54 pm

    #1356079

    It sounds like this is a new implementation. I've found that with new Sharepoint installations users madly add their old documents and the database grows very quickly initially, but once that first phase is over growth levels off significantly. Try get an idea of what the users are doing, and wait a few weeks to see if your db follows this pattern.

    Cheers

    Leo

    Leo
    Nothing in life is ever so complicated that with a little work it can't be made more complicated.

  • July 20, 2011 at 4:21 pm

    #1356090

    One of the site collections in the web application is to archive district documents and photos. It makes the database grow quickly

  • July 21, 2011 at 7:57 am

    #1356391

    Interesting. We are about to go with Sharepoint 2010 here.... I can't wait!......... Based on the size of our company will will easily have a 1TB db.

  • July 21, 2011 at 8:58 am

    #1356480

    sqlfriends (7/19/2011)

    Thanks,

    but sorry I provided wrong information.

    The database now is 116 gb, and it gorws 6 gb every week.

    Not knowing anything specific about managing SharePoint portal applications or databases, a growth rate of 6 GB per week sounds excessive. First confirm a few quick things like what pecentage of the total database size is used and index fragmentation percentages. Also, see if there are any administrative reports in SharePoint that indicate things like the total number of documents archived over time, top X largest documents, what users are the checking in the most content, and what type of files they are archiving.

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

  • July 21, 2011 at 9:02 am

    #1356486

    We have begun conversations with Microsoft and an implementation partner and this is in line with expectations. There are a bunch of modules within Sharepoint and depending on which ones you implement and how much people actually put into sharepoint you could see huge growth spikes. Especially if you just turn it on or have a group of people starting to use it and putting a ton of things into it. Based on the little conversation we have had we will be planning for a large implementation here. We did a base install two weeks ago for 4 people to kick the tires and play with it.

  • July 21, 2011 at 9:35 am

    #1356531

    I don't know about your SharePoint environment, but where I work we use it mostly for publishing documents, typically MS Office or PDF documents. One thing to keep in mind is that the new DOCX and XLSX document formats (which internally are XML content compressed using Zip algorithm) can be 5x or 10x smaller than the same content saved in backward compatible DOC or XLS files. This is significant, especially when users are frequently uploading revisions on a daily basis and the content for prior versions are retained in history.

    http://blogs.msdn.com/b/joelo/archive/2006/12/12/new-office-file-format-real-world-word-size-example-family-christmas-letter.aspx

    "Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho

Viewing 15 posts - 1 through 15 (of 16 total)

You must be logged in to reply to this topic. Login to reply