Closed byroniac closed 5 years ago
We rely on .Net Core's SqlClient library here. They have an open issue for this but it's unlikely that it will be addressed since SQL 2005 is not supported. See https://github.com/dotnet/corefx/issues/15424 for more. Unfortunately the best I can recommend is to use Windows or use other utilities as a workaround like you have been
Thank you for that link. Hindsight being 20/20, we should have upgraded long ago.
I believe that you need SQL Server 2005 upgraded to SP4 in order to run. There was a breaking security change that affects 2005 and 2008 servers where in .Net Core, it intentionally will not connect to a server without that change applied. Therefore, updating to that usually solved it for previous folks who had this problem.
Well, we're actually on one of the cumulative updates post-SP4 (not the latest, so maybe CU2, if CU3 is the latest). Thanks for the info. I am very hesitant to patch a server to fix a client problem when I'm basically the only one with a problem.
Have tried every way I know of to connect to a default instance of SQL 2005. I realize that version is not supported any more. But we will begin the process of upgrading to a SQL 2016 server soon, and it would be very nice to connect to this older SQL server. For whatever it is worth, the "sqsh" utility is able to connect, but it is not using the same connection driver.
Steps to Reproduce: