RDLC report in MVC throwing out of memory exception if the records are more than 65000

Question

1.00/5 (1 vote)

See more:

If my records in rdlc is more than 65000 records it is throwing out of memory exception in mvc using .net...How to resolve this error

What I have tried:

I am calling RDLC Report from MVC, if the records are less than 65000 it is not giving any error, how to resolve this error

Thanks
Mishrutha

Posted 19-Mar-18 20:18pm

Divyay208

Updated 20-Mar-18 3:51am

Add a Solution

Comments

Richard Deeming 20-Mar-18 9:53am

REPOST
This seems to be exactly the same question you posted back in December:
https://www.codeproject.com/Questions/1220585/How-to-export-thousound-records-into-csv-file-or-r[^]

Divyay208 22-Mar-18 2:14am

yes but that time also I did n't find any solution so instead of RDLC I used CSv file , but now I want to display data in RDLC then user can export data into EXCEL file

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Richard Deeming · Answer 1 · 2018-03-20T03:52:00

Solution 1

Simple: don't try to load that much data into memory.

There's no way a user is going to look through a list of 65000 rows. Even if they could look at one row per second, it would take them over 18 hours without a break to read the report.

Find a way to filter or summarize the data, so that the user can see what they need without having to waste a whole day looking for it.

Posted 20-Mar-18 3:52am

Richard Deeming

Comments

Divyay208 22-Mar-18 2:11am

I am using filters to minimize the data but client exporting data into excel and he want to upload same data into their system so I have to show full data depends on their date filters

Richard Deeming 22-Mar-18 8:12am

Then don't use Reporting Services; execute the query, and stream the results directly to a CSV file.

Divyay208 25-Mar-18 6:05am

There were data format issues in CSV File,especially for the numbers and date fields that is why i am using reporting services

Richard Deeming 26-Mar-18 13:53pm

It would be far simpler to fix the data format issues in the CSV export.