Cognos inflating the file size of CSV's

[civicman4]

I have a scheduled report that runs as a CSV and then emails itself to a group of users.  It recently started sending out blank files.  I discovered the reason for this is because the file sizes for the CSV output were too large go through Exchange.  When I ran the report manually as a CSV and saved the output to my desktop, the file was half the size of what it was coming from the scheduled report with the same parameters.  Is there a way I can get Cognos not to inflate the size of the CSV file before it tries to send it out in an email?

[Grim]

This is very peculiar. I'd run a UDA trace on the scheduled report as well as the manual run and compare the SQL to make sure that it is in fact the same.

Same as any other ipf trace just using ipfudaclientconfig.xml.sample.

[civicman4]

My report is calling a stored procedure that I wrote in SQL Server so all the Cognos generated SQL should be pretty limited.  Does this information help at all?  Is there a setting I missed that I should enable when using a stored procedure?

[Grim]

Shouldn't be any different. If the Stored Proc is run in both the manual and scheduled run then the SQL should be the same. The csv should also be the same size regardless.

That said there are advanced properties you can enable for email limits.
https://www-304.ibm.com/support/docview.wss?uid=swg21453903

Edit:
More links...
This one might be better than the original one posted.
https://www-304.ibm.com/support/docview.wss?uid=swg21375131

10.1 Docs
http://publib.boulder.ibm.com/infocenter/cbi/v10r1m0/index.jsp?topic=%2Fcom.ibm.swg.im.cognos.ug_cra.10.1.0.doc%2Fug_cra_id9356asg_max_attachment_size.html

[MMcBride]

Conjecture on my part I will admit...

however, in Cognos 8.4.1 CSV is really a subset of Excel Web based output which caused huge file sizes, we had one report that when run in Cognos and saved was 84 MB then if you opened it in Excel and simply saved as a real Excel doc was under 4MB in size.

In Cognos 10.1.1 this has been adressed and the file sizes are much smaller as a result - but the question is where did they impliment the change?

If you schedule a report to run and email the results are you saving the document as part of the schedule?
If not perhaps it is in the Save action where they trimmed the size of the file - essentially removing all the excess html junk.

An easy test would be to run the report without emailing it - look at the archived versions and see the size if the archived versions are much larger then when you run it manually open up a ticket to IBM because this is a bug.

If the Archive version is small (like when you manually run it) then create a "job" instead of a schedule - run the report and save it but don't email it - then the next step in the job email the last archived version.

just a few ideas