Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Microsoft Python Driver for SQL Server

github.com

Post reply on HN
Print view View original

31–35 of 35 posts

Re: Microsoft Python Driver for SQL Server

#31

Post by ludamn »

RaftPeople wrote: post #15
abirch wrote: post #3

What my workself would love is to easily dump Pandas or Polar data frames to SQL Tables in SQL Server as fast as possible. I see this bcp, but I don't see an example of uploading a large panda dataframe to SQL Server.

> What my workself would love is to easily dump Pandas or Polar data frames to SQL Tables in SQL Server as fast as possible We run into this issue also where we want to upload volumes of data but don't want to assume access to BCP on every DB server. We wrote a little utility that actually works pretty fast compared to other methods we've tested (fast=about 1,000,000 rows per minute for a table with 10 random columns…

Thanks for the detailed insight

Re: Microsoft Python Driver for SQL Server

#32

Post by bormaj »

I'd love to see a production grade release of this package with async and BCP support. MSSQL has always been a second class citizen (and rightfully so) amongst its open source peers and now it's nice to see MS dedicating resources to this project. They've got some catching up to do, but the alpha benchmarks look quite promising so far!

Re: Microsoft Python Driver for SQL Server

#33

Post by tugberkk »

brewmarche wrote: post #17
__mharrison__ wrote: post #5

Very cool. Used to be a huge pain to connect to sqlserver from Python (especially non Windows platforms).

I have very limited Python experience but I remember using pymssql in the past. Are there any problems with it?

I use it on Windows (and Linux) but can't get it to work on M1 chips.

Re: Microsoft Python Driver for SQL Server

#34

Post by cafard »

gigatexal wrote: post #25
stackskipton wrote: post #20

Earlier quoted context omitted.

Money here means this won’t happen. Sure, greenfield does not use MSSQL but there is a ton of companies stuck with MSSQL that will continue to have to fork over big licensing money.

Which will mean it’ll stay irrelevant still.

Irrelevant to whom? The accounting department at my old employer, which uses Great Plains/Dynamics for accounts payable? Next time I'm downtown I'll tell the comptroller that she should get with the program and run AP out of Maria DB.

Re: Microsoft Python Driver for SQL Server

#35

Post by razakel »

gigatexal wrote: post #25
stackskipton wrote: post #20

Earlier quoted context omitted.

Money here means this won’t happen. Sure, greenfield does not use MSSQL but there is a ton of companies stuck with MSSQL that will continue to have to fork over big licensing money.

Which will mean it’ll stay irrelevant still.

SQL Server is hardly an also-ran.
Post reply on HN