Home Forums Article Discussions Article Discussions by Author Discuss Content Posted by Joseph Sack Capturing The Error Description In A Stored Procedure RE: Capturing The Error Description In A Stored Procedure

  • July 25, 2008 at 1:59 pm

    #848684

    sql_er (7/25/2008)

    Guys,

    I have noticed a few things happening with the excel spreadsheet, as I am using this approach:

    1. The excel file is increasing in size, even though the data inserted does not grow in size (as if so

    2. If I inserted 1000 rows yesterday, and today i run the DTS package, which clears everything out and inserts 200 rows, I get 800 empty rows after it, with the size of the Excel spreadsheet either same as 1000 row one or even more

    3. Sometimes empty rows are just added on and on every time I run this report

    Has anyone encountered any of these problems and could point to a solution?

    Thanks a lot!

    I recall that being one of the issues that led me to my approach as I described earlier in this thread. I think the fix though, was to manually name the range with the table name with only the field names in the first row, and ranging rows 1 and 2. Then using a transformation to fill the excel table after the delete statement. Something like that. Try my approach instead. It's much cooler.

    [font="Courier New"]ZenDada[/font]