Showing posts with label sql2005. Show all posts
Showing posts with label sql2005. Show all posts

Thursday, 22 March 2012

connect to named instance in a cluster

Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
I have a N+1 cluster and installed default sql instance and one named
instance. SQL Browser service is running on the node which owns the named
instance; UDP port 1434 is opened on the firewall.
I had problem connecting to the named instance. Then I found the port number
in the sql error log which the named instance listens on. Opening this port
in firewall solved the connection problem.
My questions:
1. What's the best/secure way to connect to the named instance in a cluster?
Why does it not work with UDP opened and SQL Browser running before the
specific port is opened?
2. Will the port number change when the sql instance restarts? If yes, how
to assign a static port number?
Thanks.
Claudia
The short answer is that the behavior you observed is perfectly normal.
SQL will decide on a port when the service restarts unless it is a default
instance or you have locked SQL to a specific port number.
You can use the SQL Server Configuration Tool to "lock" the instance to a
specific port. This is done whenever a client needs a static port to
connect to.
Geoff N. Hiten
Senior SQL Infrastructure Consultant
Microsoft SQL Server MVP
"Claudia" <Claudia@.discussions.microsoft.com> wrote in message
news:17766F0D-BF9B-4DA1-9D1A-126B57E422B4@.microsoft.com...
> Windows 2003 N+1 cluster, SQL2005 enterprise + sp2
> I have a N+1 cluster and installed default sql instance and one named
> instance. SQL Browser service is running on the node which owns the named
> instance; UDP port 1434 is opened on the firewall.
> I had problem connecting to the named instance. Then I found the port
> number
> in the sql error log which the named instance listens on. Opening this
> port
> in firewall solved the connection problem.
> My questions:
> 1. What's the best/secure way to connect to the named instance in a
> cluster?
> Why does it not work with UDP opened and SQL Browser running before the
> specific port is opened?
> 2. Will the port number change when the sql instance restarts? If yes, how
> to assign a static port number?
> Thanks.
> Claudia

connect to MSSQL2005 via ODBC

Installed SQL2005, connect via (the new) SQL Nativ Client ODBC Vers. 2005.90.1399.00 works, just as (the old) SQL Server ODBC-Driver 2000.85.1117.00. Works fine.
But from an other machine -there is no client installed - using driver 2000.85.1117.00 I get the message "Server dosn't exist or access denied"
How I can connect ? It is due to the fact of .NET FRAMEWORK 2 ?
Thanks!Sounds like the 'other' machine is your first network client - check your enabled protocols with SQL Server Configuration Manager.

Also, check your connection details include the instance name if necessary.

Also, what are the OS levels and authentication method?|||Hi, Mulhall. Indeed, it's the first network client W2K, connections to other sql2000 servers are o.k., to SQL2005 tried using TCP/IP-Protocol, tried Named Pipes and all others. Using the standard instance, no named, using SQL-authentication such as win-authentication, tried connection by server-name and by IP-Adress. OS-Ping works normaly.|||Have you verified using the Surface Area Configuration tool that remote connections are enabled?

Thanks
Laurentiu|||Thanks Laurentiu, upon configuration Surface Area Conf.Tool the connection works. I did not know this featureIdea

Tuesday, 20 March 2012

Connect to DB using another TCP port from SQL management Studio

Hi,
The DBA set database on server to a high TCP port number.
How can I connect to it from Microsoft SQL2005 management Studio.
I can't find the option to set TCP port number in there.
Thanks!You can use tcp:servername,port in the connection dialog although if the SQL
Browser is running you should still be able to use the instance name. As an
alternative you can set up a client alias using SQL Server Configuration
Manager>SQL Native Client Configuration>Aliases
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<walanta> wrote in message
news:loure2pjt4o6rvq7t5r3rvh4mln76i3pan@.
4ax.com...
> Hi,
> The DBA set database on server to a high TCP port number.
> How can I connect to it from Microsoft SQL2005 management Studio.
> I can't find the option to set TCP port number in there.
> Thanks!|||Where is "connection dialog" ?
I'm using SQL server management studio-> object explore-> connect->
database engine -> ...
I see "servername:", "authentication:", "connect to database:",
"network protocol"...
No place I can put "tcp:192.168.1.1,8800" or somthing like that.
On Thu, 24 Aug 2006 22:08:36 +0100, "Jasper Smith"
<jasper_smith9@.hotmail.com> wrote:

>You can use tcp:servername,port in the connection dialog although if the SQ
L
>Browser is running you should still be able to use the instance name. As an
>alternative you can set up a client alias using SQL Server Configuration
>Manager>SQL Native Client Configuration>Aliases|||Hi,
Go to SQL Server program groups nad select "SQL Server Configuration
Manager"
Thanks
Hari
SQL Server MVP
<walanta> wrote in message
news:ndcse2lg3v26uv0s31sh8sob6rl84l9tq4@.
4ax.com...[vbcol=seagreen]
> Where is "connection dialog" ?
> I'm using SQL server management studio-> object explore-> connect->
> database engine -> ...
> I see "servername:", "authentication:", "connect to database:",
> "network protocol"...
> No place I can put "tcp:192.168.1.1,8800" or somthing like that.
>
>
> On Thu, 24 Aug 2006 22:08:36 +0100, "Jasper Smith"
> <jasper_smith9@.hotmail.com> wrote:
>|||It's in the Server name box i.e. if your server was called FOO and on port
55551 you would use
tcp:FOO,55551
in the Server name box
HTH,
Jasper Smith (SQL Server MVP)
http://www.sqldbatips.com
<walanta> wrote in message
news:ndcse2lg3v26uv0s31sh8sob6rl84l9tq4@.
4ax.com...[vbcol=seagreen]
> Where is "connection dialog" ?
> I'm using SQL server management studio-> object explore-> connect->
> database engine -> ...
> I see "servername:", "authentication:", "connect to database:",
> "network protocol"...
> No place I can put "tcp:192.168.1.1,8800" or somthing like that.
>
>
> On Thu, 24 Aug 2006 22:08:36 +0100, "Jasper Smith"
> <jasper_smith9@.hotmail.com> wrote:
>|||If SQL Browser is started you should be redirected automatically. For
security reasons (and the fact that this is not enabled in the setup
process by default) the SQL Browser service can not be running. The
port can be specified manually by putting it after the instancename you
want to connect to:
For default instances: Servername\InstanceName,Portnumber
For named instances: Servername,Portnumber
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
--