Omg it’s sooo daammmn slooow it takes around 30 seconds to bulk - insert 15000 rows

Disabling indices doesn’t help. Database log is at SIMPLE. My table is 50 columns wide, and from what i understand the main reason is the stupid limit of 2100 parameters in query in ODBC driver. I am using the . NET SqlBulkCopy. I only open the connection + transaction once per ~15000 inserts

I have 50 millions rows to insert, it takes literally days, please send help, i can fucking write with a pen and paper faster than damned Microsoft driver inserts rows

  • GetOffMyLan
    22·
    3 months ago

    No. This seems like a poorly designed system. Definitely sounds like a nosql database would be a much better fit for this task.

    And that many parameters seems like madness haha

    • kSPvhmTOlwvMd7Y7EOP
      24·
      3 months ago

      Please enlighten us? You barely know anything about the system or usage, and you have deduced nosql is better? Lol

      • GetOffMyLan
        71·
        3 months ago

        A flat 50 column table is usually an indicator of bad design and lack of normalization.

        Nosql is absolutely ideal for flat data with lots of columns and huge amounts of rows. It’s like one of its main use cases.

        That many parameters is an indicator of poorly structured queries and spaghetti code. There is no way that’s the best way the data can be structured.