System.OutofmemoryException

  • When I run my report I get:

    System.OutofmemoryException

    It's a pretty big SQL statement from about 8 tables.

    Is there any memory I need to release or something along these lines?

    Thanks!

  • "It's a pretty big SQL statement from about 8 tables"

    So does putting the query into a stored procedure help? What sort of formatting, etc... is in the report?

    How much data are you trying to squeeze into the report? If the report is many, many pages long, then thinking logically, is the report useful? Would it be better seperated into smaller reports?

     

    --------------------
    Colt 45 - the original point and click interface

  • The report, unfortunately, is suppossed to give the user all the data so they don't have to go in and print for individual IDs.

    I'm using a list object for all the data.

  • How much data do you have to present (mbs, rows, columns, size of rows).

  • 26930 rows

  • How much data is that in MB or GB?

  • How can I find that out in query Analyzer.....datalength(spReport)

    I'm trying the query in a sproc...spReport, but when I run it in the Report Manager to preview the report, it doesn't like my alias table "I".  Heres' the query:

    SELECT     I.*, WP_Budget.[Historical Budget], WP_Budget.FY04, WP_Budget.FY05, WP_Budget.FY06, WP_Budget.FY07, WP_Budget.FY08, WP_Budget.FY09,

                          WP_Budget.FY10, WP_Cost_Codes.[Program Code], WP_Cost_Codes.[Cost Account], WP_Cost_Codes.[WP Number], WP_Deliverables.P3ActivityId,

                          WP_Deliverables.[Deliverable Description], WP_Deliverables.Date AS DeliverablesDate, WP_Milestones.P3ActivityId AS MilestonesP3ActivityID,

                          WP_Milestones.[Milestone Description], WP_Milestones.[Milestone Level], WP_Milestones.Date AS MilestonesDate,

                          WP_Deliverables.[Deliverable Number], WP_Milestones.[Milestone  Number], Signature_Authority.Title, Signature_Authority.Person,

                          Signature_Authority.SigAuthNbr

    FROM         WP_General_Info I INNER JOIN

                              (SELECT     MAX(WP_Package_Identifier) AS Expr1, [WBS Number]

                                FROM          WP_General_Info

                                GROUP BY [WBS Number]) G ON I.WP_Package_Identifier = G.Expr1 INNER JOIN

                          WP_Budget ON I.WP_Package_Identifier = WP_Budget.WP_Package_Identifier INNER JOIN

                          WP_Cost_Codes ON I.WP_Package_Identifier = WP_Cost_Codes.WP_Package_Identifier INNER JOIN

                          WP_Deliverables ON I.WP_Package_Identifier = WP_Deliverables.WP_Package_Identifier INNER JOIN

                          WP_Milestones ON I.WP_Package_Identifier = WP_Milestones.WP_Package_Identifier INNER JOIN

                          Signature_Authority ON I.WP_Package_Identifier = Signature_Authority.WP_Package_Identifier

    ORDER BY I.[WBS Number]

     

    Thanks for the help!

  • Simplest way is number_of_rows * avg_size_of_row.

    Let's say the avg row size is 1 K, that's over 27 MB of raw data to transfer/present (god knows how much bloating that can cause)... Does the server have enough ressources to handle that?

  • If I take out my last table, Signature_Authority, where I'm only pulling three fields, the report will run with about 219 pages.

    I'm trying to figure out the average size of each row...but no luck yet.  There are aparently setting in query Analyzer, but I'm not doing something right.

  • It's not a setting, it's a formula. But it doesn't matter now, I have a vague idea. Looks like if you can't change the report, then you'll have to find to failing hardware and replace/upgrade.

  • I just changed the list object to page break on the grouping (so basically the change of the Unique ID will go to another/new page), and now the report is working.  It'll show +1100 pages.

    Weird.........

  • Not really if you show 5 times less data per page.

  • Yeah...good point.  Less data / page, but more pages.

  • Still a strange problem... looks like you found a bug in the grouping section of the program.

  • I have had this issue in a previous company.

    When you start coming up in the thousands of pages, (Can;t remember the actual number) Reporting services will crap out.

    We went all the way to Microsoft, and they noted thats not what reporting services was for.

    You will probably have to figure out some way to make your report "smaller".

     

Viewing 15 posts - 1 through 15 (of 17 total)

You must be logged in to reply to this topic. Login to reply