Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Database & SysAdmin
  3. Database
  4. SqlClient will not connect to 2005 SqlServer

SqlClient will not connect to 2005 SqlServer

Scheduled Pinned Locked Moved Database
csharpdatabasesysadminquestion
2 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    ianhoc
    wrote on last edited by
    #1

    OleDb connects fine? VS2005; C#; SQL 2005 Developer (remote server) SqlClient connection string: "data source=MyRemoteServer;user id=MyUserID;password=MyPassword;initial catalog=DbName;workstation id=PC1" OleDb connection string: "provider=SQLxxxx;data source=MyRemoteServer;user id=MyUserID;password=MyPassword;initial catalog=DbName;workstation id=PC1" (xxxx = I forget the exact provider string) OleDb connects fine, SqlClient times out looking for the server? Am I missing something obvious? Should I really worry about this - I thought SqlClient was faster and better? Thanks Ian

    P 1 Reply Last reply
    0
    • I ianhoc

      OleDb connects fine? VS2005; C#; SQL 2005 Developer (remote server) SqlClient connection string: "data source=MyRemoteServer;user id=MyUserID;password=MyPassword;initial catalog=DbName;workstation id=PC1" OleDb connection string: "provider=SQLxxxx;data source=MyRemoteServer;user id=MyUserID;password=MyPassword;initial catalog=DbName;workstation id=PC1" (xxxx = I forget the exact provider string) OleDb connects fine, SqlClient times out looking for the server? Am I missing something obvious? Should I really worry about this - I thought SqlClient was faster and better? Thanks Ian

      P Offline
      P Offline
      Paul Conrad
      wrote on last edited by
      #2

      Did you get this to work?

      "Any sort of work in VB6 is bound to provide several WTF moments." - Christian Graus

      1 Reply Last reply
      0
      Reply
      • Reply as topic
      Log in to reply
      • Oldest to Newest
      • Newest to Oldest
      • Most Votes


      • Login

      • Don't have an account? Register

      • Login or register to search.
      • First post
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • World
      • Users
      • Groups