CONFIGURING SQL SERVER

SQL NATIVE CLIENT CONFIGURATION

SQL NATIVE CLIENT is a Provider used to Connect with server Four server-side protocols are supported for the SQL Native Client

Aliases can be created using the SQL Native Client Configuration. Aliases are very useful in enabling clients to connect to a server even though the name of the server does not match that in the clients connection string. Replace a complicated named instance name.

SQL SERVER ENDPOINTS

A SQL Server endpoint is the point of entry into SQL Server.
It is implemented as a database object that defines the ways and means

communicate over the network. SQL Server 2008 routes all interactions with the network via endpoints and each endpoint supports a specific type of communication. A SQL Server endpoint is a useful point where one can enhance the security of a SQL Server 2008 installation. If, for example, you want to allow your DBAs to monitor a production database from afar then you'll need to set up remote access to a Server via the internet that only your support team can use. This is where endpoints come in. Endpoints, which are a general term for the point of connection between a client or server and the network, can be used in SQL Server in much the same way as a firewall, in order to limit the type of traffic to just what you, as administrator, expect and want. The advantage of a user-defined endpoint is that traffic must be authorized before it even reaches SQL Server. If you are implementing SOAP-based services, mirroring or Service Broker, then you are probably already up to your elbows in endpoints. They are essential for security. SQL can listen on different ports, using dif. Protocols for dif. Services .

in which SQL Server may

SQL Server provides four different types of endpoints: TSQL Database Mirroring SOAP Service Broker

Each endpoint provides separate functionality and can be uniquely configured to control access to the database engine and associated services.

DEFAULT TSQL ENDPOINTS

During installation, five TSQL endpoints are created: TSQL Default TCP TSQL Default VIA TSQL Named Pipes TSQL Local Machine Dedicated Admin Connection (DAC)

 The

TSQL endpoints are created to provide connection services for the four supported protocols (TCP, VIA, Named Pipes, and Shared Memory). These protocols correspond to the Default TCP, Default VIA, Named Pipes, and Local Machine endpoints. The fifth endpoint created to support the DAC listens on a dedicated TCP port that is configured at startup to support an administrative connection when other connections are unavailable or unresponsive. go Create endpoint ep State=started As tcp(listener_port=50102,listener_ip=all) For tsql(); go

 TSQL endpoints have two states: started and stopped.

If

the network protocol is enabled and the endpoint is started, SQL Server will listen and accept connections on that endpoint. A stopped endpoint still listens, but actively refuses new connections. If the corresponding protocol is disabled, the TSQL endpoint will not listen and will not respond to client requests.

DATABASE MIRRORING ENDPOINT

Database

mirroring is a primarily software solution for increasing database availability. Mirroring is implemented on a per-database basis and works only with databases that use the full recovery model. The simple and bulk-logged recovery models do not support database mirroring. Database mirroring is supported in SQL Server Standard and Enterprise. Database mirroring offers substantial availability and provides an easyto-manage alternative or supplement to failover.

Create endpoint ep State=started As tcp(listener_port=50102,listener_ip=all) For data_mirroring(authentication=windows,encryption=required algorithm rc4);

SOAP ENDPOINTS
Simple

Object Access Protocol (SOAP) is a platformindependent protocol that defines how to use XML and HTTP to access services, objects, and servers. SOAP endpoints are created to publish SQL Server programming objects over data tier Web services without the use of IIS as a Web server. Creating data tier Web services with SOAP endpoints requires Windows Server 2003 or Windows XP Professional.

CREATE ENDPOINT endPointName [ AUTHORIZATION login ] STATE = { STARTED | STOPPED | DISABLED } AS HTTP ( PATH = url , AUTHENTICATION =( [ ,...n ] ) , PORTS = [, COMPRESSION = { ENABLED | DISABLED } ] )

FOR SOAP ( [ ( NAME = database.schema.name

[ , SCHEMA = { NONE | STANDARD | DEFAULT } ]

[ , FORMAT = { ALL_RESULTS | ROWSETS_ONLY | NONE} ] ) } [ ,...n ] ]

SERVICE BROKER ENDPOINTS

With Service Broker, a feature in Microsoft SQL Server 2008, internal or

external processes can send and receive guaranteed, asynchronous messages by using extensions to Transact-SQL Data Manipulation Language (DML). asynchronously communicate with other database applications. Service Broker endpoints are only required if the two instances of the broker service are located on separate instances of SQL Server.

USE Master; CREATE ENDPOINT MyEndpoint STATE = STARTED AS TCP ( LISTENER_PORT = 50001 ) FOR SERVICE_BROKER ( AUTHENTICATION = WINDOWS );