I've ran into similar issues like this before -- but on different databases.
I think it's bad to think of the problem as "transmitting 31k/s" -- which assumes a particular issue; and much better to think of it as "processing 31k/s", which gives a lot more room for interpretation. Looking on StackOverflow and it's related sites, it seems that Sql Server also falls victim to the usual patterns: • The database doesn't like the format of the data or configuration (it takes up too much memory, there are too many constraints, etc) • The driver isn't appropriate for the type of data I'm guessing that this issue is with the driver. Here's a semi-related thread: * http://stackoverflow.com/questions/5693885/pyodbc-very-slow-bulk-insert-speed It looks like the pyodbc driver handles "executemany" in a not very ideal manner. There were also some threads that noted ODBC tracing being on, and others that noted most python drivers are just painfully slow. In any event, if you're talking about a single insert statement.... that sounds like an executemany context and a driver issue. -- You received this message because you are subscribed to the Google Groups "sqlalchemy" group. To unsubscribe from this group and stop receiving emails from it, send an email to sqlalchemy+unsubscr...@googlegroups.com. To post to this group, send email to sqlalchemy@googlegroups.com. Visit this group at http://groups.google.com/group/sqlalchemy. For more options, visit https://groups.google.com/d/optout.
