Does sp_dropuser “do the right thing” with schemas?
Here's another blog posting to answer a question from over a month ago. With separation of users and schemas, its known that the CREATE USER
Menu
Here's another blog posting to answer a question from over a month ago. With separation of users and schemas, its known that the CREATE USER
When I discuss separation of users and schemas in SQL Server 2005, I usually think of ownership chains (that follow the object owner which is
I've answered a few questions lately on setting up SqlDependency or ASP.NET SQL Server dependency with SQL Server 2005. Folks have gone by the instructions
In answering a question about schemas, users, and objects (search on "schemas" to see the blog series I, II, III), I realized I never posted
Now, back to our regularly scheduled technical content. About schemas, users, and owners. Although Ed originally created the table, since Fred is the schema owner,
The code for the answer is below. Greg Low is, of course, correct. Fred owns the table, but he owns it by virtue of being
UI can't stay away from the separation and users and schemas feature. I want to make sure I have it cold, and following up on
More on user-schema separation. In SQL 2000 and previous versions, granting someone CREATE TABLE privilege meant that they could create tables (no surprise there). The
Separation of users and schemas is another cool SQL Server 2005 feature, but it has some interesting behaviors that folks may have to get used
With training and consulting from SQLskills, you’ll be able to solve big problems, elevate your team’s capacity, and take control of your data career.