Loading
How can I use named-pipes to connect to local SQL server 2005
Hi,

 

I experience a problem with connections to the (local) SQL server 2005 (express edition). From our software, we solved this problem by using "np:" as part of the connection string (SERVER=np: (local)\INSTANCE).

 

However, I also have this problem during installation - we need to run SQL scripts as part of the installer. Now when I try to set the "Default Target Server Name" property of the connection element, adding np: to the server string does not work when I run the installer.

 

My question - how can I force the connection to use named-pipes? Another option - if someone already had this problem - how else can I make the connection to the local SQL more consistent?

 

Thx,

 

Ron

  • 0_H Yamanishi (Flexera Software)

    InstallShield uses the Win32 Winsock TCP/IP network library by default. In order to change it to the Win32 Named Pipes, you need to modify the AdoCxnNetLibrary column of the ISSQLDBMetaData table as follows:

     

    From:

     

    Network Library=DBMSSOCN

     

    To:

     

    Network Library=DBNMPNTW
    Expand Post

Loading
How can I use named-pipes to connect to local SQL server 2005