Am using Windows Server 2008R2,In this C:/ Drive Space getting increase

  • Dear All,

    I know this is some what get irritate to you,Very sorry for that but i hope that you can give me some suggestions for This.

    Am using Windows Server 2008R2,

    In this Server C:/ drive space is getting increase day by day

    as per my knowledge i have to format that system.

    If is there any other chances to get space and remove unwanted things from my Server.

    Please help me out on this..

    Regards...

    Regards
    Chowdary...

  • without more details, all we can do is guess.

    the most likely culprit is you have databases that have the recovery model set to FULL, but are failing to take regular log backups.

    AS soon as you take your first FULL backup of a database in FULL recovery, the log will grow, until you run out of disk space, OR you take a log backup.

    now there could be lots of other things eating up drive space, but that's a common issue that it should be looked at first.

    Lowell


    --help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!

  • Along with Lowell's suggestions, I'd take a look at what files are changing day to day. Search on updated files, see if you can track what is using more space or what's new.

    Then we can guide you on possible solutions.

  • Thank you all,

    In my system SQL server was installed,

    My DB Log size is 32GB now ,DB is in Full Recovery model.

    Day to Day Log size is getting increasing.

    If I take a Log backup then the size of Log will reduce or not?

    Regards..

    Regards
    Chowdary...

  • Ofcourse, taking a log backup actually truncates the the .ldf and prevents it to grow physically, I would recommend you to create a maintenance plan for the log backup and a clean up task as well.

    :-):-):-)

  • After you have a regular maintenance plan in place and are truncating everything, you can still manually shrink the data files on the database to get them back to regular levels. I would only do this once to recover that space and then let the files grow and float around normal operating sizes. You don't want to make this regular practice since it will just impact performance by forcing growth to occur or worse if the data isn't allowed to grow automatically, but once to recover that space wouldn't be too bad.

  • Consider Using Ola Hallgrens backup solution to handle full and Tlog backups in your environment. It works great. a 32GB log file can not only fill up your drive and cause a database and system crash (in your case because it is on the OS drive), but it also means that because you have millions of VLFs (Virtual log files), it will take forever to recover from an instance crash or become online after a recycle of the sql service or a patch / update application. Managing the log file is easy but can be tricky so making sure you have freqeunt log backups with truncate is the key. You will have to shrink after the first log backup so you can reclaim the space for the C drive.

    Also, one important question would be; WHY IS THE DB IN FULL RECOVERY MODEL? I would imagine that if it was to prevent data loss, a TLOG backup would have been a regular practice so i believe i can safely and correctly assume that it wasn't intentional. Consider using simple recovery model if disk space isn't a luxury for you. Else, go with the above suggestions.

    GOODLUCK...

  • Thank you All for sharing your valuable Knowledge .....

    Regards
    Chowdary...

Viewing 8 posts - 1 through 7 (of 7 total)

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