Question

I have a Silverlight web application.

I am inserting records into a table (SQL Database), loaded from a csv file.
I tried loading +- 15 000 records and it throws me out with the following error:
The remote server returned an error: NotFound.

I gather it is because it is just too much data to insert at once because when I split it into ‘batches’, say 100 at a time, it inserted into the table no probs. Even 500 at a time was too much.

What I do after I insert it into the table, is read from that same table the data and put it into a datagrid. This is so the user can see that it was inserted successfully and also monitor as the records that were inserted are processed.

Now obviously I am getting the same error when attempting to load the 15000 +- records back to a datagrid.

My question is how can I read the records in the table also in batches?

Hope somebody can help.

Many thanks,

Neill

EDIT

To test I made a change to the OperationContract:

Originally

[OperationContract]
public List<send_box> GetSendingItems()
{
    return (from a in smsData.send_boxes
            orderby a.sb_log descending
            select a).ToList();
}

Changed To

[OperationContract]
public List<send_box> GetSendingItems()
{
    List<send_box> sendBoxList = (from a in smsData.send_boxes
            orderby a.sb_log descending
            select a).ToList();

    return sendBoxList;
}

The result are returned from the database, but when I try to return it to the application:
–> return sendBoxList

Then it throws out the “The remote server returned an error: NotFound.” error. Hope this extra info will assist

Regards

Neill

Answer 1

I am not sure what is your exact business requirement. But going by one of your response, you said user wnats to see all the records. I am not sure what the user would be able to do if all the 15,000 records fail. May be it would be a good idea to show a kind of summary saying out of lets say 15000, 10000 passed and 5000 failed. And provide drill down or navigation link to explore the success or failure records.

Secondly, even though user wants to see all records, I don’t think its user friendly to display more than 100 records in a grid. 100 is also extreame for me. You can implement paging functionality to limit the number of records displayed in the grid.