How to post huge data using WCF service with stored procedure?

Question

0.00/5 (No votes)

See more:

, +

Hello,

I have created a WCF service using stored procedure.

[WebGet]
        public List<View_JobAssign> AssignJobs(string employeeId, string assignDate, string jobs, string userId)
        {
            try
            {
                TrackerEntities entities = new TrackerEntities();
                return entities.AssignJobs(Convert.ToDateTime(assignDate), Convert.ToInt32(employeeId), jobs, Convert.ToInt32(userId)).ToList();

            }
            catch (Exception ex)
            {
                throw new DataServiceException(ex.Message + ex.InnerException);
            }
        }

The data which I pass to above service is
employeeId = 1, assignDate = "2017-02-22", Jobs="1,2,3", userid = 1
and it works like charm.
But the problem is when I try to pass Jobs = '1,2,....10000' i.e upto 10000 which makes a long string then I get HTTP request Failed Error.

How do I pass data to stored procedure created service with long data?
is there any alternative?

What I have tried:

I tried to use reflection provider with Entity Framework but it doesn't work.

Posted 16-Feb-18 2:43am

Member 13681529

Updated 18-Feb-18 15:55pm

Add a Solution

Comments

Richard Deeming 16-Feb-18 13:11pm

Are you getting a "request entity too large" error? If so, you'll need to increase the maxReceivedMessageSize on your binding.

If you're getting a different error, then you'll need to give us the details of that error.

Also:

throw new DataServiceException(ex.Message + ex.InnerException);

Don't do it like that; you've just thrown away the interesting details of the exception. Use:

throw new DataServiceException(ex.Message, ex);

Member 13681529 22-Feb-18 2:08am

Yes, I am getting below error when I tried to run on browser.
Request URL Too Long
HTTP Error 414. The request URL is too long.

And then I tried the same on Rest Client. Then it said HTTP Error 400 - Bad Request.
Also, I tried maxReceivedMessageSize to 2147483647, but the issue is same.

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)

ZurdoDev · Answer 1 · 2018-02-18T15:55:00

As Richard mentioned you would need to search google for the exact error you are getting because there are settings you can change depending on what limit you are exceeding.

However, to me, the more obvious suggestion is to cut down on how many you send at once and just loop to send smaller amounts.