-
Notifications
You must be signed in to change notification settings - Fork 435
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does tedious support localdb? #348
Comments
I guess you're talking about SQL Server Express LocalDB? If yes, this should be supported, as it's basically a slimmed down version of SQL Server. But no guarantees, as I never used that version before. Did connecting to your LocalDB instance work before? |
I use it for testing, here is the info on it:
I am using this to connect to it:
|
Ah, ok, I now understand your issue.
Another issue is that from my understanding, native TDS drivers from microsoft will start your localdb instance if it's not already running. So overall, I stand corrected. As-is, |
Ah, awesome to know. Sounds like TDS solves a specific problem which is great. I agree that named pipes are another issue altogether. |
Thanks for the information posted here. I too am looking to implement a solution where I would need to connect to localdb. |
Did anyone solve this question with another approach? |
Hello! I was in the middle of writing a migration script in node when I got this error:
So, my question is, does this work with a localdb instance? My gut feeling tells me no but wanted to ask anyway.
The text was updated successfully, but these errors were encountered: