How to upload big file to DB with webpage?

[Grace]

Hello,

I want to upload the file by webpage to SQL Server.

When I upload the small file, it is work.
But, when I upload big file(ex. 40~50 MB), it isn't work;
the Browser displays the following error message:
"The webpage consulted at present is unable to use.
Websites may happen the technological question or you need to adjust the
browser to establish ."

I test it,
reading file to byte array is ok, but import byte array to DB is error.
I add "Connect Timeout=300", it still has this error.

What do this error mean?
And how to solve it?

Thanks for your help.

[Bob Powell [MVP]]

Uploads done through an HTTP POST are subject to the maximum request size.
In most cases this is 4096 k (4 megs).

If you have control over the server you can change the MaxRequestSize
setting in machine.config. if not you'll have to collaborate with whoever
runs the server to create a page that enables you to send chunks of a file
in smaller portions.

If it's not a POST issue then I don't know what to suggest.

--
Bob Powell [MVP]
Visual C#, System.Drawing

Find great Windows Forms articles in Windows Forms Tips and Tricks
http://www.bobpowell.net/tipstricks.htm

Answer those GDI+ questions with the GDI+ FAQ
http://www.bobpowell.net/faqmain.htm

All new articles provide code in C# and VB.NET.
Subscribe to the RSS feeds provided and never miss a new article.

"Grace" <Gr***@discussions.microsoft.com> wrote in message
news:40**********************************@microsof t.com...

Hello,

I want to upload the file by webpage to SQL Server.

When I upload the small file, it is work.
But, when I upload big file(ex. 40~50 MB), it isn't work;
the Browser displays the following error message:
"The webpage consulted at present is unable to use.
Websites may happen the technological question or you need to adjust the
browser to establish ."

I test it,
reading file to byte array is ok, but import byte array to DB is error.
I add "Connect Timeout=300", it still has this error.

What do this error mean?
And how to solve it?

Thanks for your help.

[Praveen]

This problem can be due to two different cause:
1. Your file is not fully being uploaded.
2. Your logic to update database server is taking too long.
Let me address prblem number one. Solution for this problem lies in
web.config file. Add following section:

<httpRuntime
maxRequestLength="40000"
executionTimeout="1800"
/>

maxRequestLength is request size in kb and executionTimeout is in seconds.
Hope this makes sence to you.
To find out if the problem is of second type, you divide your process into
two. First only try to upload the file, if it is successful, that means your
database update logic is taking long. If this is the case, post your
database update logic here, we will optimize it.

-Praveen

[Ignacio Machin \( .NET/ C# MVP \)]

Hi,
Put this in your web.config

<httpRuntime maxRequestLength="100000" ></httpRuntime>

Cheers,

--
Ignacio Machin,
ignacio.machin AT dot.state.fl.us
Florida Department Of Transportation

"Grace" <Gr***@discussions.microsoft.com> wrote in message
news:40**********************************@microsof t.com...

Hello,

I want to upload the file by webpage to SQL Server.

When I upload the small file, it is work.
But, when I upload big file(ex. 40~50 MB), it isn't work;
the Browser displays the following error message:
"The webpage consulted at present is unable to use.
Websites may happen the technological question or you need to adjust the
browser to establish ."

I test it,
reading file to byte array is ok, but import byte array to DB is error.
I add "Connect Timeout=300", it still has this error.

What do this error mean?
And how to solve it?

Thanks for your help.

[Grace]

Thanks.
I think Server's RAM seems to be larger.
But, when the RAM is 1GB, it still can't save bigger file into SQL Server.
I test that it only upload about 4xMB file into SQL Server.

Does it use the memory of the Web Server when user upload the file?
Does it use the memory of the Web Server when the uploaded the file( in the
memory(byte array) ) saves into DB?

Thanks again.

"Praveen" wrote:

Web form is not going to wait for 40mb byte[] load to complete. This method
is going to have very bad performance result when multiple users accessing
different services on your server. I suggest a logic change than a technical
solution. Divide the process into two.
1. Upload the file, using your present method, to a pre-defined folder on
the server.
2. Write a separate program to load all the files on that folder to the
database server and delete them.
According to your requirement, (ie, how fast you need the data on the
database)
a. run this program as scheduled task (may be at night)
b. or run it as a server service, using FileSystemWatcher on that folder,
to load files as they arrive.

If you need the user to be notified how successful the upload were, may be
you can collect the email address of the user and send status emails from
your upload program.

I suggest this program to be run from a separate computer considering amount
of memory it will require.

-Praveen

[Praveen]

for a short period, untill SaveAs() method finish its work. After that when
you load the data to byte array, it is again stored on server memory.
Having seen your question on the news group, I decided to post my past
experiance of solving a smilar problem in uploading file. Only difference is
that my file was MS Access (.mdb) database file. I have used slightly
different approach here. My server now is receiving upto 20 MB files using
this method. May be my experince help you with more ideas.

http://www.kpraveen.com/uploadMdb2Sql.htm

-Praveen

"Grace" wrote:

Thanks.
I think Server's RAM seems to be larger.
But, when the RAM is 1GB, it still can't save bigger file into SQL Server.
I test that it only upload about 4xMB file into SQL Server.

Does it use the memory of the Web Server when user upload the file?
Does it use the memory of the Web Server when the uploaded the file( in the
memory(byte array) ) saves into DB?

Thanks again.

"Praveen" wrote:

Web form is not going to wait for 40mb byte[] load to complete. This method
is going to have very bad performance result when multiple users accessing
different services on your server. I suggest a logic change than a technical
solution. Divide the process into two.
1. Upload the file, using your present method, to a pre-defined folder on
the server.
2. Write a separate program to load all the files on that folder to the
database server and delete them.
According to your requirement, (ie, how fast you need the data on the
database)
a. run this program as scheduled task (may be at night)
b. or run it as a server service, using FileSystemWatcher on that folder,
to load files as they arrive.

If you need the user to be notified how successful the upload were, may be
you can collect the email address of the user and send status emails from
your upload program.

I suggest this program to be run from a separate computer considering amount
of memory it will require.

-Praveen