Hi! I’m currently working with

tap-mssql

using the default

wintersrd

variant. I searched the repo for a

start_date

but it seems there isn’t any. Has anyone had any success running this tap limiting the date of the data? I searched open issues or PR but couldn’t find any that address this issue. Thanks!

cc @visch @david_tout

I haven't needed incremental myself, I'm no help here 😕

Thanks @aaronsteers and @visch, the reason we are looking to restrict the date is that for some older data (outside the current need of the business) we’re getting the following error: “corrupted unsorted chunks” with both FULL and INCREMENTAL which fails the extraction

hmm https://stackoverflow.com/questions/39417641/reason-and-solution-of-error-in-python-free-corrupted-unsorted-chunks

I tried it with Airbyte to see if it was inherently part of the database but the extraction ran successfully… not sure how to make it work with Meltano

I think that implementation uses pymssql so it smells of that bug

Thanks @visch! I saw a PR on the tap repo for an upgrade to 2.2.1, and even @aaronsteers asked for an update on the this particular PR but it seems it safer to switch pymssql for pyodbc

Yeah I think that's the way. I have a target-mssql written with pyodbc, but not a tap

I’ll talk with my team to see if we can make this work for the tap 🤞

Good luck, I will say my migration from pymssql to pyodbc was pretty seemless

Good to know, thank you for taking the time! @visch

No problem, let us know what fix you go with!

I'm running in incremental mode, but I did not try and limit how far back the data went