Jump to content

frapetti

Members
  • Content Count

    10
  • Joined

  • Last visited

Profile Information

  • Location
    Argentina
  1. For what i readed, SQL Server Native Client (SSNC) shouldn't be used anymore for new developments, and instead use new clients that replaced it. That's why there aren't any new SSNC versions. The last one was from 2012. Maybe ESET could do that, and then the problem would go away. See: https://docs.microsoft.com/en-us/sql/connect/connect-history?view=sqlallproducts-allversions
×
×
  • Create New...