Connection Pooling

Setting the maximum size of the connection pool is usefull if you suspect that you have blocking problems due to the large number of concurrent queries. In this case you may be able to reduce blocking by limiting the maximum size of the connection pool. Of course, the pool already limits the number of concurrent connections, so you may never encounter this problem.

Master database Transaction log backup can not take.

Only full database backups of master can be performed. Transactional log, differential or filegroup backups of master are not allowed. Thus if you create a Database Maintenance Plan for all the system databases or if you select the master database and you select the Back up the transaction log as part of the maintenance plan option, the backup transaction log step for the master database will fail with this error message:

SQL Server Instance connection using Client tool

If SQL Server Instance is not named Instance then you can connect using the below any option for connection.

1.ServerName.domainName.com,PortNumber
or
2.IPNUmber,PortNumber
10.20.30.40,1590

SQL Server Interview questions

1. http://blog.sqlauthority.com/2007/04/21/sql-server-interview-questions-and-answers-complete-list-download/
2.http://www.techinterviews.com/ms-sql-server-interview-questions
3.http://www.mssqltips.com/category.asp?catid=46
4.http://vyaskn.tripod.com/iq.htm
5. http://dayananthan.wordpress.com/2008/01/20/sql-server-interview-questions/
6.http://www.codeproject.com/KB/database/SQLInterviewQuestions.aspx

Database Mirroring Setup Steps

You need to perform the following prior to start database mirroing:
1. Take a full backup in principal database and copy it to mirror server
2. Restore the principal database using With NORECOVERY option
3. Take a single transaction log backup in principal servers database and copy it to mirror server
4. Restore that single t-log backup using With NORECOVERY option and start mirroring,
it should work..

SQL Server Agent jobs setup minimum permissions

SQL Server 2005 introduced the following msdb database fixed database roles, which give administrators finer control over access to SQL Server Agent. The roles listed from least to most privileged access are:
SQLAgentUserRole
SQLAgentReaderRole
SQLAgentOperatorRole


http://msdn.microsoft.com/en-us/library/ms188283.aspx

To find out users and roles on SQL Server Instance

--users and roles on SQL Server Instance
sp_helplogins