Home Forums SQL Server 2014 Development - SQL Server 2014 How does SQL Server handle concurrent operations? RE: How does SQL Server handle concurrent operations?

  • February 27, 2018 at 6:24 pm

    #1981391

    junk.mail291276 - Tuesday, February 27, 2018 4:52 PM

    Hello,

    We are having an issue which I suspect is database related. We have a web application on which we can upload files. When we upload a file, data from that file gets saved to a SQL database. We also have a web API that reads from that database. Recently, we discovered that when I upload a file, during the time that file is uploading, the API responds with a general error (internal server error 500).

    We are wondering if maybe our database is configured to handle only one operation at a time; that is, maybe while it is save data from the file, it is too tied up to service any requests for data from the API.

    Is there any way to check for this in the database settings/configurations?

    What method(s) are you using to upload the file and what kind of file is it?  Also, how long is it taking to upload the file and, if it's row based, how many rows and what is the average length of each row?

    --Jeff Moden

    RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
    First step towards the paradigm shift of writing Set Based code:
    ________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.

    Change is inevitable... Change for the better is not.

    Helpful Links:
    How to post code problems
    How to Post Performance Problems
    Create a Tally Function (fnTally)