Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Am using Windows Server 2008R2,In this C:/ Drive Space getting increase Expand / Collapse
Author
Message
Posted Tuesday, April 29, 2014 6:16 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 1:41 AM
Points: 99, Visits: 296
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...
Post #1565878
Posted Tuesday, April 29, 2014 6:28 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Yesterday @ 7:44 AM
Points: 12,910, Visits: 32,015
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

--There is no spoon, and there's no default ORDER BY in sql server either.
Actually, Common Sense is so rare, it should be considered a Superpower. --my son
Post #1565884
Posted Tuesday, April 29, 2014 8:39 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Yesterday @ 5:56 PM
Points: 33,202, Visits: 15,348
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.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #1565969
Posted Tuesday, April 29, 2014 10:57 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 1:41 AM
Points: 99, Visits: 296
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..
Post #1566207
Posted Wednesday, April 30, 2014 1:04 AM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Thursday, August 21, 2014 5:51 AM
Points: 50, Visits: 265
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.


Post #1566235
Posted Wednesday, April 30, 2014 4:25 AM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Monday, May 12, 2014 9:06 AM
Points: 7, Visits: 54
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.
Post #1566290
Posted Friday, May 2, 2014 10:12 PM


SSC Rookie

SSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC RookieSSC Rookie

Group: General Forum Members
Last Login: 2 days ago @ 7:43 AM
Points: 45, Visits: 377
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...
Post #1567210
Posted Monday, May 5, 2014 12:04 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Wednesday, August 27, 2014 1:41 AM
Points: 99, Visits: 296
Thank you All for sharing your valuable Knowledge .....
Post #1567413
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse