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

Space Issue in C drive Expand / Collapse
Author
Message
Posted Tuesday, December 17, 2013 3:35 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 22, 2014 12:58 AM
Points: 16, Visits: 59
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 .....

Post #1523587
Posted Tuesday, December 17, 2013 3:43 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 2:04 AM
Points: 5,380, Visits: 9,945
What is the recovery mode of your database? Do you have transaction log backups set up?

John
Post #1523589
Posted Tuesday, December 17, 2013 4:09 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 13,017, Visits: 10,799
And why o why do you keep your log files on your C drive?
That is waiting for disaster to strike.




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1523598
Posted Tuesday, December 17, 2013 4:11 AM
Right there with Babe

Right there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with BabeRight there with Babe

Group: General Forum Members
Last Login: Today @ 12:16 AM
Points: 752, Visits: 1,323
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

Post #1523599
Posted Tuesday, December 17, 2013 5:08 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 22, 2014 12:58 AM
Points: 16, Visits: 59
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)


master 0.7421875 56.44737 0
tempdb 1.492188 54.54843 0
model 0.4921875 89.88095 0
msdb 0.9921875 60.28543 0
ReportServer$MHBCPACCHAD 6.867188 19.0273 0
ReportServer$MHBCPACCHADTempDB 1.054688 69.39815 0
MHBCPACCHAD 0.9921875 47.78543 0
MHBCPACCHAD_Testing 0.9921875 66.97835 0
SSISDB 8014.742 93.30867 0
Post #1523610
Posted Tuesday, December 17, 2013 5:16 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 22, 2014 12:58 AM
Points: 16, Visits: 59
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..
Post #1523614
Posted Tuesday, December 17, 2013 5:28 AM


SSChampion

SSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampionSSChampion

Group: General Forum Members
Last Login: Today @ 7:35 AM
Points: 13,017, Visits: 10,799
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?




How to post forum questions.
Need an answer? No, you need a question.
What’s the deal with Excel & SSIS?

Member of LinkedIn. My blog at LessThanDot.

MCSA SQL Server 2012 - MCSE Business Intelligence
Post #1523621
Posted Tuesday, December 17, 2013 5:33 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Monday, September 22, 2014 12:58 AM
Points: 16, Visits: 59
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
Post #1523626
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse