Recently, I've been discussing security in SQL Server 2000. In my February column, "Crossing the Line: Ownership Chains" (InstantDoc ID 40963), I talked about the limitations of ownership chaining and the additional security concerns inherent in cross-database ownership chaining. In my April column, "Object Ownership and Security" (InstantDoc ID 41773), I talked about the confusions and limitations surrounding SQL Server 2000's model, which doesn't separate the concepts of user and schema. This month, let's look at some security enhancements in SQL Server 2005, formerly code-named Yukon, that address these security limitations.

Mic...