January 14, 2005 at 8:29 am
Ok here si the setup
I have two servers. Each serverhas an SQL instance for each program that we run on SQL 2k.
SO that makes 4 instances besides the default on each server. We use a special program that copies the data realtime to the other server so that we can have a fail safe if the one server goes down automatically. (kind of like clustering but a lot cheaper.) well the issuse is that even with the sql service for the instances stopped on the other server everyone can see those instances in the DSn or if running a crystal report. SO it ends up being 8 different servers in the list. Is there a way to hide some instances from showing up on the list?
Instances On Want hidden
server1/Program 1 Yes No
Server2/Program1 No Yes
Etc.
Thanks,
A
January 17, 2005 at 12:11 am
Maybe this is what you are looking for :
SQL Server Network utilities (Server-box)
TCPIP-properties
Hide server
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 17, 2005 at 12:37 am
This forces the instance in question to tcp/2433. As a result, only one instance can be hidden in this manner. What you can do is block all traffic to/from udp/1434 for the server using an IPSec policy. Unfortunately, this will block providing this information for ALL instances. Also, one would have to connect to a named instance using the TCP port (server1,1234 instead if server1\server1).
K. Brian Kelley
@kbriankelley
January 17, 2005 at 12:47 am
Hi Brian,
You'll off course have to select the server-instance which you want to alter the tcpip properties.
I have a server with 3 virtual instances and all 3 are listed in the listbox at the SQL Server Network utilities pane (at the Server-box).
This means You can manage tcpip visibilite per instance.
Because of earlier problems with hidden servers (mdac/ado) I have not enabled "hide" at my servers.
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 17, 2005 at 3:44 pm
Brian,
Do I understand correctly that "This forces the instance in question to tcp/2433" means that if I want to hide the instance but have programs still be able to connect using the explicitly set connection properties then I have to open Port 2433 where applicable?
Yelena
Regards,Yelena Varsha
January 17, 2005 at 9:50 pm
Yes, if you've got tcp/2433 blocked and you switch on Hide Server, you'll need to open up access to that port. That's one of the flaws with the Hide Server setting. It puts the SQL Server on tcp/2433 and there's no way around it. Since SQL Server needs exclusive access to that listening port, that's why no multiple instances are allowed.
K. Brian Kelley
@kbriankelley
January 18, 2005 at 12:01 pm
Thanks. This may (or may not) resolve a couple of mystery connection drops that one of our port admins discovered in his monitoring tool
Regards,Yelena Varsha
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply