A connection pool is a cache of database connections maintained by the database so that the connections can be reused when the database receives future requests for data.
In today's demanding applications, creating new connections for each user request from scratch, maintaining them, and tearing down the open connection is costly. Drawing from the pool eliminates this overhead. Connection pooling increases the performance of Web applications by reusing active database connections instead of creating a new connection with every request.
A connection pool is a cache of database connections maintained by the database so that the connections can be reused when the database receives future requests for data. Some of the myths concerning connection pooling and the truth behind those myths are given below:
Myth 1: Changing the connection string, even slightly, will force a new connection.
Truth: Its False.
Windows Authentication in SQL Server is managed by domain accounts while Mixed Mode Authentication uses both Windows Authentication and SQL Server Authentication.
While installing SQL Server you might see an option similar to the one below
Master is the most important database in SQL Server. The following procedure has been tested and it works however we do not provide any guarantees. Please use it at your own risk.
Following are the steps to restore the Master database in SQL Server 2000:
sp_fulltext_database can be used to enable or disable full text indexing on current database. Only members of the db_owner fixed database role can execute sp_fulltext_database.
In order to enable full text indexing, please execute the following code in the Query Analyzer after replacing NorthWind with your database name:
sp_fulltext_catalog creates and drops a full-text catalog, and starts and stops the indexing action for a catalog. Multiple full-text catalogs can be created per database.
Following is the example of executing the sp_fulltext_catalog which should be run in the Query Analyzer.