|
Home > Archive > SQL server exams > August 2002 > Connecting to Named Instances
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Connecting to Named Instances
|
|
| Ryzor 2002-07-30, 10:34 pm |
| I am currently studying out of the Readiness Review study guide for 70-228 and on the bottom of page 33 it states: "Clients cannot connect to SQL Server 2000 running named instances"
Is this correct? If so, then what are named instances good for?
----------------------
Also, the question of the day a few days ago was the following:
SQL Server uses which port to establish connections from SQL Server 2000 clients?
A) UDP port 1434
B) TCP port 1434
C) UDP port 1433
D) TCP port 1433
E) UDP port 1432
F) TCP port 1432
Given Answer: A. According to the MS SQL Server BOL: SQL Server uses UDP port 1434 to establish connections from SQL Server 2000 clients. This socket number is also reserved for SQL Server by Internet Assigned Number Authority (IANA).
Isn't this incorrect...shouldn't it be good 'ol port 1433?  | |
| dlayne76 2002-07-31, 9:48 pm |
| the names instances part is only referring to situations when you are using multiprotocol net library....
and yes i do believe that port 1433 is the default... | |
| necrophantasm 2002-08-01, 8:00 am |
| As far as the named instances and connections are concerned, I think the other poster is right about the multiprotocol connection. Named instances themselves though are advantageous because they allow multiple installations of SQL on a single server (as opposed to the default instance you install the first time around). So if there are any major banking companies out there with their data warehouses and farms, they can take advantage of the named instances to create multiple SQL Server configurations based on their product needs on a single server. | |
|
| In other words, when you select a named instance, only the Named Pipes, TCP/IP, and NWLink IPX/SPX protocols are supported. The Multiprotocol Net-Library is not supported with named instances.
The Question of the Day is correct. According to the MSDN Library SQL Server uses UDP port 1434 to establish connections from SQL Server 2000 clients. It just "listens" on port 1433 for the upload side and downloads to the client on port 1434. Right?
Regarding port 1433: I have just learned that it is the most scanned port the world over for hacking purposes. There is a short technical article from VeriSign called "Hacking and Network Defense" that demonstrates the allure of MS SQL Server for it vulnerabilities. |
|
|
|
|