how to read large amount of data with OleDbDataAdapter

Question

0.00/5 (No votes)

See more:

I have excel file which have 2,20,000 records and 40 Mb Size..i want to read this excel file with OleDbDataAdapter and store result into dataset in asp.net with c#...this is perfectly running in my local machine but when i deploy this application in IIS 7, i cant read data from this large excel -file, i already change the web config also and also test with small data its working with small amount data.. i think it is issue of large amount of data...Can you plz help me to solve it out? is that any changes done in IIS 7 or not regarding this ?

Posted 12-Feb-14 0:24am

Yagnik_Vishal

Add a Solution

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)

OriginalGriff · Answer 1 · 2014-02-12T01:07:00

Two things spring to mind: firstly that your IIS setup has a limited application memory pool, and your app may be exceeding that. The other is that it is just taking too long to process them all.

The first place I'd start is with the IIS server logs[^] to identify where the bottleneck is.

But...if you load 220,000 records into a dataset, I do hope you aren't trying to display them all - as that is what is known in web site design circles as "user hostile" or "just plain dumb".