Hello All, I have very simple question. Recently I was just checking table spaces in our database and I found that dbo.sysdtslog90 table has significantly large size. Upon Googling I found that this table is used by SSIS to log details of package execution, which is more like a log of execution of SSIS packages. I know that We have few SSIS packages in production, and they are being used from past few years. And I think because of that table is of so large size. So my question is, can I remove entries from this table ... or atleast delete few records ?? Also, what are the "side effects" if I choose to remove entries ?? Any suggestions is really appreciated. Thanks, -Jack

Afaik this is a normal table and you can delete older entries from that without side effects. I suggest a SQL Server Job which deletes the older entries periodically

How large is the table? Do you have any auditing requirements/policy in house? Since this table is a sys table it was not really meant for "intervention" after all deleting records at the time when packages run may create an issue. E.g. you create a deletion job today to say remove records at 1am, forget about it later and a new package gets deployed to execute at 1 am, what will happen? My suggestion is to leave it along unless this table spoils something.Arthur My Blog

Thank you guys for your so quick response.... @Arthur .. I totally agree with you that we should not play with System tables. But the table size is more than 6Gb and it has more than 19Mil records. And it is one of the reason I want to reduce the size since it actaully is increasing size of database and its backups. And as far as I remember I don't think we have any audit policy for that task being done by SSIS packages. Also, I dont want to drop the whole table, instead I am just thinking to remove older transactions (say all transaction older than 1 year)... Regarding deployment of the package question: When I deploy new package will it automatically start logging its history in dbo.sysdtslog90 table ?? Or at some place I need to configure it to do so ?? Because, I don't think currently anyone is even trying to log package execution info anywhere other than SQL Server Agent Logs or Windows event logs. Thanks, -Jack

This sure tells there is a ton of redundant info in there. These are packages that log into this table, besides, it is the default SQL side destination for the SSIS 2005 packages to log to.Specifically a log provider will log, but not automatically. So further to this: What I suspect is happening - the packages were designed to log too much and I would redesign that behavior. If no audit/prod monitoring is in place, then by all means, delete the old data. Arthur My Blog

Yes, that's what I am going to do soon. I am thinking that if we are not using this log for audit then I will just stop the log getting piled up with history (But I am not the only one to make this decision). But thanks for your reply. This was the answer I was looking for. -Jack