Repository navigation
SqlClient: Keyword not supported: 'TransparentNetworkIPResolution' #99
Description
From @msmolka on March 10, 2017 12:50
I'm sharing connection string between net462 and core application.
connection string contains `TransparentNetworkIPResolution=False;'
When starting ASP NET Core app I have following error:
Exception message: An exception occurred in the database while saving changes.
Stack trace:
Microsoft.EntityFrameworkCore.DbContext[1]
An exception occurred in the database while saving changes.
System.ArgumentException: Keyword not supported: 'transparentnetworkipresolution'.
at System.Data.Common.DbConnectionOptions.ParseInternal(Dictionary`2 pa
I'm expecting TransparentNetworkIPResolution is proper keyword.
Further technical details
EF Core version: 1.1.1
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows Server 2012
IDE: Visual Studio 2015
Copied from original issue: dotnet/efcore#7836
Activity
divega commentedon Mar 10, 2017
From @ErikEJ on March 10, 2017 13:42
It is not implemented in .NET Core (yet)
https://github.com/dotnet/corefx/search?utf8=%E2%9C%93&q=TransparentNetworkIPResolution
(and no related issue either)
[-] Keyword not supported: 'TransparentNetworkIPResolution'[/-][+]SqlClient: Keyword not supported: 'TransparentNetworkIPResolution'[/+]saurabh500 commentedon Mar 20, 2017
TNIR will be supported after 2.0
AlexaCodex commentedon Feb 27, 2019
Is this supported yet and on which version?
divega commentedon May 16, 2019
As recently announced in the .NET Blog, focus on new SqlClient features an improvements is moving to the new Microsoft.Data.SqlClient package. For this reason, we are moving this issue to the new repo at https://github.com/dotnet/SqlClient. We will still use https://github.com/dotnet/corefx to track issues on other providers like System.Data.Odbc and System.Data.OleDB, and general ADO.NET and .NET data access issues.
chrisjsmith commentedon Jul 13, 2022
+1 on this issue. We're getting 40,000 timeouts a day from .Net Core processes and latency spikes because this doesn't exist. Any chance of implementing it before the sun explodes?
David-Engel commentedon Jul 19, 2022
@chrisjsmith
I'm curious how the lack of TNIR is causing your issues. Do you have any more details on your configuration and experience that you can share?
Past experience with customers is that TNIR has caused more connectivity headaches than it has solved compared with using MultiSubnetFailover when the environment warrants it. So we have not prioritized bringing TNIR to the .NET Core side of the SqlClient driver. We may bring the keyword to the connection string for compatibility, but it would be a no-op setting.
JRahnama commentedon Apr 9, 2023
@chrisjsmith any update if the issue still exists in M.D.SqlClient latest release?
jrichardsz commentedon May 24, 2023
Any update?
MichelZ commentedon Nov 8, 2024
Do I read this right that this feature will not get implemented?
If so, maybe it's time to close this issue out :)