[recentdarkness]

I wanted to use it as well on windows the other day. Because I wanted to migrate a mssql database to PostgreSQL. However AFAIR there were no builds I could find and from what I read in the issues it is quite discouraging, a pity

[jhgb]

I've just loaded pgloader successfully on 64-bit Windows into SBCL 2.1.8 straight from Quicklisp. The only snag was that I needed sybdb.dll (which I got from https://github.com/ramiro/freetds/releases), and that in turn required OpenSSL (which I got from https://www.npcglib.org/~stathis/blog/precompiled-openssl/). Then, with sysdb.dll on the path, it loaded correctly. Haven't tried how it works, though. I don't even have an MSSQL installation, so there's that.

[gavinray]

Use the Docker image, here's a tutorial written by someone I helped migrate MySQL to Postgres entirely in Docker (because they also had troubles with running it locally):

https://dev.to/narayandreamer/mysql-to-postgres-migration-us...

I recommend the Docker image over downloading and running it locally anyways tbh -- you can just prune Docker images to remove stuff without needing to remember to delete it, and you don't have to copy it to your bin dir in PATH.

[jamal-kumar]

You have two options in this case, tacking on an mssql or general db connect library is asking a lot of a tool made by one guy in lisp.

First is writing your own tool with the connector libraries working fine on windows sql server in the lang of your choice which is great if you have to do transformation on the data for whatever reason while you are importing - the second is dumping from mssql to csv, then loading it in, which is honestly the KISS way to go as long as that is all you need to do.

Best of luck!

[mey]

The best way I have found to work with the tool is the docker image. This brings up an entirely new issue of docker on windows and bridging localhost access, so replacing one problem with another.