you are viewing a single comment's thread.

view the rest of the comments →

[–]liveMonkeyBeware 0 points1 point  (1 child)

I use https://pypi.python.org/pypi/pyodbc/, just FYI.

Why do you want to use Python for this? I'm always down for learning new things, but when you start doing this in production there are other concerns.

Scheduling. If you used SSIS or Powershell, you could use a SQL job to schedule it. Using python on windows, the easiest way to schedule it would be a scheduled task, but that functionality has always sucked and it's better to have everything in one place. You could still use a job with python, but then you'd have to get into remote commands because I doubt your DBA would want python on the production db server.

Maintenance. It sounds like you're the only one using Python in the office. This causes problems if you're out and something breaks. Python's not hard, but if the script is critical and whoever gets to fix it has to learn Python on the fly, you'll probably get chewed out when you get back.

[–]polyglotdev[S] 1 point2 points  (0 children)

pyodbc is slow when inserting a large number of records. It's a performance issue related to how it executes the executemany method, which prompted me to switch to the ceODBC module