• 2 Posts
  • 26 Comments
Joined 1 year ago
cake
Cake day: June 17th, 2023

help-circle











  • 2100 parameters is a documented ODBC limitation( which applies on all statements in a batch)

    This means that a

    “insert into (c1, c2) values (?,?), (?,?)…” can only have 2100 bound parameters, and has nothing to do with code, and even less that surrounding code is “spaghetti”

    The tables ARE normalised, the fact that there are 50 colums is because underlying market - data calibration functions expects dozens of parameters, and returns back dozens of other results, such as volatility, implied durations, forward duration and more

    The amount of immaturity, inexperience, and ignorance coming from 2 people here is astounding

    Blocked



  • I timed the transaction and opening of the connection, it takes maybe a 100 milliseconds, absolutely doesn’t explain ghe abysmal performance

    Transaction is needed because 2 tables are touched, i don’t want to deal with partially inserted data

    Cannot share the code, but it’s python calling .NET through “clr”, and using SqlBulkCopy

    What do you suggest i shouldn’t be using that? It’s either a prepared query, with thousands of parameters, or a plain text string with parameters inside (which admittedly, i didn’t try, might be faster lol)