DBDATASOLUTIONS
asked on
Visual Studio 2005 SSIS Maintenance Plan Task Issue with Transaction Log Backup
I must be doing something stupid. My transaction log task in my Maintenance Plan Task Step called Transaction Log Backup will not hold the settings for selected databases to be backed up. So, my transaction log files never get truncated and I run out of disk space. We installed a new application 2 weeks ago and now the .ldf file grows to about 50 gig and chews up the disk space. Of course I now how to backup the log manually, but I was wondering if there was a fix for this. I recently installed the critical patch for SQL Server 2005 SP2. This did not correct it. I think it is more of an issue with the properties of the step within my SSIS package that does the database maintenance. See attached screen shot.
2008.10.24-Issue-with-the-ssis-p.jpg
2008.10.24-Issue-with-the-ssis-p.jpg
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I was able to go back into SSIS and get the value to persist. It did not always persist though. I tested it many times. Finally I got one to persist and after confimation that that deployed version worked I left it alone. I dont have time today to write the TSQL to "Do it by hand". Anybody got the script they can post or e-mail to dbdatasolutions@gmail.com? Thank you to Mark Wills and 4Beers!!
Greg Bogard
Greg Bogard
Maybe thats just since I'm using a Maintenance Plan using the SMSS, not deploying with SSIS. Is there any way you could try it with a Maintenance Plan rather than using SSIS.
One more thing, from memory, if you have multiple steps in the SSIS package, have you linked them using the arrows so it does each step (just a random thought - sorry if this sounds stupid, not even sure if that matters!).