Post reply

ERROR: System is low on disk space on drive ‘C’, All SQL profiler functions are temporarily disabled

  • January 9, 2007 at 2:29 am

    #176419

    We got error ‘System is low on disk space on drive ‘C’, All SQL profiler functions are temporarily disabled’ in SQL profiler and SQL profiler was stopped during nightly load test run. Following is the more detail.

     

    SQL Server 2000 SE with SP3a is only installed with OS Windows 2000 on the box with following configuration.

    Model Dell PE2650, with 2 * CPU Xeon(R) CPU 5110 @1.60GHz with Hyper Threading Enabled, 3.8 GB RAM 

    Disk drive information is as below.

    C: drive : Total: 4GB, Free :1.31GB contains windows binary and trace templates of SQL server

    D: d: drive : Total: 12GB, Free :6:01GB contains SQL server binary and swap space drive.

    E: drive : Total: 120GB, Free :82.5GB Application and system datafiles and transaction log files.

     

    There were two SQL profilers are running, one with Stored Procedures RPC:completed  and TSQL- SQL: BatchCompleted event class to find out total execution duration of Stored procedure and SQL statement.

     

    Another SQL profiler were running parallel to capture duration, read, write , CPU Of detailed SQL statement within stored procedure with Stored Procedure : SP:Stmtstarting and SP:StmtCompleted event class.

     

    The trace results are diverted onto table which are located on in a database whose datafiles are on E: drive where enough disk space is there

     

    We have started around 18:30pm trace and it is stopped around 4:00 am early next day with above error.

     

    We have ran many load test in past also, but never got any such error.

     

    What could be the exact reason for this error?

    How C: drive will play roll in such case?  As free space on this drive generally remain constant.

     

    Please let me know your view.

     

    Thanks in advance.

    Regards

    Ghanshyam Borasaniya

    Sr DBA

    gborasaniya@asite.com

  • January 9, 2007 at 6:15 am

    #681995

    I think profiler still creates files even if writing to a table. I'd have thought the message was clear enough  although another process could have required disk space.

    [font="Comic Sans MS"]The GrumpyOldDBA[/font]
    www.grumpyolddba.co.uk
    http://sqlblogcasts.com/blogs/grumpyolddba/

Viewing 2 posts - 1 through 1 (of 1 total)

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