One of the first posts I did, and a popular one, based on the statistics was a video on how to configure SQL Server 2005 for VC. This post provides an update to that same idea but with the added bonus of showing how to configure VC to use Windows Authentication to a remote SQL Server 2005 system.
While the video shows configuration with VC update 1 it still holds true for the Update 2 that was released this past weekend (7/24/2008).
The video shows the following steps:
1. Creation of SQL Server user account.
2. Creation of VC database.
3. Configuration of SQL Server user account.
4. Install of SQL Native Client
5. Creation of ODBC connection.
6. Install of VC 2.5.
7. Removal of MSDB permissions for SQL Server account.
8. Creation and configuration of Windows account for VC to use for Windows Authentication.
NOTE: According to the VMware setup guide for VC it is not supported to use Windows Authentication for remote SQL access. This may change in the future, however, I can't promise or guarantee it.
I created this because I have run into a few scenarios when engaging customers where the company does not allow SQL Server authentication due to its historically bad reputation. The reality is that SQL Server Authentication can be configured to use the same security settings as the Windows domain password policy and therefore has really eliminated the age old threat of a no password SA account. Any environment wth an SA account that has no password has been purposefully configured that way.
Chris