cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

Disk Full

Former Member
0 Likes
801

In of our servers it is BI7.0 on Sqlserver 2005 and windows 2003 the disk is almost full.Could anyone assist in cleaning up of the system so that we can start the system.As of now we cannot even start the system.Thanks.

View Entire Topic
Former Member
0 Likes

Perform this steps:

Log on to the Server as Admin> double click drive> CTRL+F> on the left pane you'll see All files and folders> expand "What size is it"--> search for files "SPecify size 10000 KB and post the files which are cosuming the space.

I will expalin you what to do.

Thanks

Manny

Former Member
0 Likes

Pasted below.

BSMDATA1.mdf

BSMLOG3_Log.LDF

BSMLOG3_Log.LDF

BSMDATA3.ndf

BSMLOG1.ldf

tempdb.mdf

templog.ldf

master.mdf

msdbdata.mdf

ERRORLOG.6

Are the files which are large.Of them Data1 Data2 Data3 are the largest as expected.Thanks.

Former Member
0 Likes

Did you have installed SAP in the DB files directory?

Try to increase the space if possible else take a backup of transaction log and delete the T-log file at OS level ,startup the DB and SAP.

DB will recreate T-log file at OS level.

-Manny.

Former Member
0 Likes

SAP is installed on a separate drive which is not full.But the drive which contains the DB is nearly full because of which we cannot start SAP.How do we go about from here.

Former Member
0 Likes

Hi dudes!

First at all, please NEVER EVER delete any database file on the OS level!! You won't be able to do so, unless the SQL Server is stopped in which case you will DESTROY your database!!

Instead of that, just backing up your transaction log (TLOG) should be enough to considerably reduce the data in your TLOG, and then you will be able to shrink it. You can check notes *625546* +(Size of transaction log file is too big)+ and *421644* +(SQL error 9002: The transaction log is full)+.

Regarding your original question, and assuming that after backing up and shrinking the TLOG is not enough to run your system smoothly, you could consider shrinking also your datafiles. However this is usually not interesting and could hinder your performance (regarding this particular, please refer to [this post|, and even it would just be a workaround, as sooner or later you will exhaust your drive space.

The real solution is to add more disks to your file system and then add more data files to your database or move some of the existing ones. In this sense, please refer to *note 363018* +(File management with SQL Server)+.

And also a very important task is to reduce your tables by deleting useless information. In this sense I can only recommend you a very nice note for Basis tables, i.e. *note 706478* +(Preventing Basis tables from increasing considerably)+.; regarding application tables, I cannot tell you any suggestions, but maybe you can search for other SDN threads if you find any huge tables that should not be so extense.

At last, please remind to check always the +Microsoft SQL Server 2005 *Books Online (BOL)*+.

Cheers!!

-Jesú