Post reply

Space Issue in C drive

  • December 17, 2013 at 3:35 am

    #302462

    Hi ,

    Please need help urgently ..

    We are using SQL server 2012 version and as usually we are deploying ssis Packages in Integration services Catalog by Creating SSISDB Catalog and placed our package in separate folders for each package and

    when we are Scheduling the Package for every 2 minutes the transaction log files are storing in C.Drive in respective path C:\Program Files\Microsoft SQL Server\MSSQL11.InstanceName\MSSQL\DATA

    Because of that transaction Log files created by SSISDB the C Drive space was reducing simultaneously and after some time packages are crashing.

    so can you help me in this issue as soon as possible..

    Because of this issue we are not able to do any work .....

  • December 17, 2013 at 3:43 am

    #1673988

    What is the recovery mode of your database? Do you have transaction log backups set up?

    John

  • December 17, 2013 at 4:09 am

    #1673996

    And why o why do you keep your log files on your C drive?

    That is waiting for disaster to strike.

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • December 17, 2013 at 4:11 am

    #1673997

    Koen Verbeeck (12/17/2013)

    And why o why do you keep your log files on your C drive?

    That is waiting for disaster to strike.

    ++1, you need to move your files

    you can do the following:

    Detach the database, move the files, reattach the database.

    OR

    Use the ALTER DATABASE ... ALTER FILE to change the metadata. Take the database offline, move the files, bring the DB back online.

    Do it hurry and do not make database on C Drive from now on 🙂

  • December 17, 2013 at 5:08 am

    #1674006

    iam using recovery Mode is simple and i have done shrinking also for databases i am using also but no use..

    if we try following query i am able to see

    DBCC SQLPERF (LOGSPACE)

    master0.742187556.447370

    tempdb1.49218854.548430

    model0.492187589.880950

    msdb0.992187560.285430

    ReportServer$MHBCPACCHAD6.86718819.02730

    ReportServer$MHBCPACCHADTempDB1.05468869.398150

    MHBCPACCHAD0.992187547.785430

    MHBCPACCHAD_Testing0.992187566.978350

    SSISDB8014.74293.308670

  • December 17, 2013 at 5:16 am

    #1674010

    Databases we have created in D Drive not in C Drive and we have problem at ssis DB Catalog folder and main problem is transaction log files truncation..

    how we clean up transaction log files... which is already stored in the C.drive please help as soon as possible..

  • December 17, 2013 at 5:28 am

    #1674015

    Honny (12/17/2013)

    Databases we have created in D Drive not in C Drive

    <snip>

    which is already stored in the C.drive

    Ehrm... why would you create your databases on the D drive, but store your log files on the C drive?

    Anyway, since you are using the simple recovery model you cannot take a log backup.

    So you can either

    * shrink the log file (not really recommended)

    * allocate more space on the C drive (probably a temporary solution)

    * move the log files to a bigger disk (the way to go)

    Another question: why is the "ssisdb" creating log files?

    Need an answer? No, you need a question
    My blog at https://sqlkover.com.
    MCSE Business Intelligence - Microsoft Data Platform MVP

  • December 17, 2013 at 5:33 am

    #1674018

    PLEASE SHARE YOUR NUMBER PLEASE SO THAT I CAN EXPLAIN YOU CLEARLY WHAT THE ISSUE I WAS FACING PLZ PLEASE PLEASE

    iTS URGENT ITS URGENT

    ARE YOU CAN CONTACT ME ON 9582809916

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

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