However, SQL Server 2005 implements a distinct object to open that port
for use: an endpoint. As you can see in Figure 8-8, there are endpoints for every connection
to the database, whether it??™s a straight query, an HTTP request, and so on. All connections
are implemented as endpoints.
CHAPTER 8 n DATABASE MIRRORING 201
Figure 8-8. Database endpoints as seen at the instance level
The T-SQL command for creating an endpoint isn??™t trivial either.
CREATE ENDPOINT [Mirroring]
AUTHORIZATION [SPYGLASSTAB\jluetke]
STATE=STARTED
AS TCP (LISTENER_PORT = 5022, LISTENER_IP = ALL)
FOR DATA_MIRRORING (ROLE = PARTNER, AUTHENTICATION = WINDOWS NEGOTIATE
, ENCRYPTION = REQUIRED ALGORITHM RC4)
Not only do you have to specify the protocol, the port number, and the IP address,
but you also must define who has authorization to use the endpoint that you??™re creating,
how it authenticates requests, and whether or not encryption is required.
TAKING THE FEAR OUT OF ENCRYPTION
The first time I heard that SQL Server would include native support for encrypting communication and
actual stored data, I have to admit I panicked.
Pages:
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387