Full site membership is required for this article. Already a full member? Login here. You currently have a guest membership. You can upgrade to full site membership here (free trial available). SQL Server 2005 - Schema Definition   Article Abstract: (Vinod Kumar) Microsoft’s focus lately has been in the areas of security. And security limitation and loopholes from the previous versions are getting addressed in the latest versions of software’s. And SQL Server 2005 is no exception. In this article let we just focus on the new concept called Schema and the security implications that revolve around the same.   Read this article...

Related Articles - For Members. All Articles By Author Microsoft Expands Current Reporting Offering, Unveils Next-Generation Solutions for Reporting Microsoft Outlines Enhanced Product Line and Pricing for SQL Server 2005 Known SQL Server service packs problems Understanding Yukon Schema Separation SSWUG.ORG Sessions at the SQL Server Connections Conference SQL Server Upgrade Recommendations and Best Practices - Part 2 Troubleshooting SQL Server 2005 Management Studio Troubleshooting SQL Server Command Prompt Utilities Webcast Q&A Transcript: Reporting Services Launch (Part II) Implementing Linked Servers on Microsoft SQL Server 2005 for Accessing Data on Remote Oracle Servers

RE: SQL Server 2005 - Schema Definition
(posted: 8/22/2004 3:53:02 PM)
> "Now objects are owned by schemas. Hence, the strong binding of our code in identifying an object with the user is removed."
> "...the new concept called Schema"

While the former is reasonable enough the latter bears some elaboration, as pre 2005 MS Sql Server {Create Schema} TSQL certainly exists. It is probably most commonly used to facilitate creating interdependent Key constraint bindings.

HTH