freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Scott Laing" <webmaster AT sboe.state.az.us>
- To: <freetds AT lists.ibiblio.org>
- Subject: [freetds] Named Instances of MS SQL Server 2000
- Date: Mon, 24 Nov 2003 07:11:28 -0700
You are a genius:
you wrote:
Looking at the sample C# source code that was sent earlier:
"DANPC\\NETSDK" would get parsed into two parts:
the ServerName (hostname) - "DANPC"
the InstanceName - "NETSDK"
The UDP socket on port 1434 is connected to "DANPC" and sent the data
0x02 and the InstanceName "NETSDK". The Microsoft SQL Server SQL Monitor
listens here.
The SQL Monitor responds with the result string that I showed below.
You send and receive ASCII.
Based on the data I got for ServerName "DANPC and InstanceName "NETSDK",
I have two options of connecting to that instance:
- connect via TCP port 1335
- connect via named pipes at \\DANPC\pipe\MSSQL$NETSDK\sql\query
Basically, I have discovered how to connect to the named instance "NETSDK"
at "DANPC".
However, for a Unix client, only the TCP port really matters.
response:
I'm playing around with a remote connection for the NETSDK and couldn't
figure it out at all. Thanks for your posting.
cheers,
Scott Laing
SBOE webmaster
webmaster AT sboe.state.az.us
scottlaing AT cox.net
mobile: 480-242-2423
-
[freetds] Named Instances of MS SQL Server 2000,
Scott Laing, 11/24/2003
- <Possible follow-up(s)>
- RE: [freetds] Named Instances of MS SQL Server 2000, ZIGLIO Frediano, 11/24/2003
Archive powered by MHonArc 2.6.24.