SQL Server 2005 connections can be encrypted by the SQL Server using SSL rather then using OS level IPSec. In fact according to Encrypting Connections to SQL Server part of the connection is always encrypted…
“Credentials (in the login packet) that are transmitted when a client application connects to SQL Server 2005 are always encrypted. SQL [...]
It’s possible to Deny Connect permission to an Endpoint in SQL Server 2005. So I wondered if this would be a way disable the ’sa’ server account.
The sa account is disabled if the server only supports Windows security accounts, but is enabled if Mixed accounts are supported. Of course the recommendations are to use [...]
Again with the security, this time while workout out how SOAP HTTP Endpoints work and I have two issues with it.
First, its only possible to change the execution context of the call when it reaches the target stored procure or function and only then by defining the object using ‘Execute As’. By this time the [...]
Everyone probably knows this but to GRANT permission in SQL Server 2005 to a Windows Principle enclose the principal name in square brackets. For example:
grant connect on endpoint::sql_endpoint to [domain\name]
In fact anytime you use a Windows Principal name escape the name with [ and ] to save yourself unnecessary annoyance.
One of the neat things in SQL Server 2005 is the downgrading of the importance of users / humans.
Its no longer necessary to have a big stupid login with a big stupid password just to get an execution context or control ownership of objects, see this post for examples of both techniques.
This week I found [...]