Question about dropping owner's permissions...

From: Jason Barnett (jbarnett74_at_hotmail.com)
Date: 10/29/03 

Date: Wed, 29 Oct 2003 09:41:29 -0600

    I'm using SQL Server 7.0 and my question pertains to securing my test
machine so that developers can create objects within databases, but not
create databases themselves. I have done this by adding them to the
db_owner role for each database (about 24 of them). This would work fine if
I could easily switch ownership of all objects in the database at the time
that the developer leaves the company.
    Can anyone help me reach my end goal: Allowing developers to create
objects but not databases, and easily switch the owner?

Relevant Pages

  • RE: Access user-friendliness needs to improve
    ... We professional developers some times think perhaps too much. ... Dave Hargis, Microsoft Access MVP ... As an office manager I am creating databases for my office but am keeping ... People don't make the transition because the transition is too hard to make ...
    (microsoft.public.access.reports)
  • RE: Access user-friendliness needs to improve
    ... Good post, Sunrise. ... hope of creating jobs within our structure for Access developers. ... are some fairly complex databases around that have no VBA at all, ... Administrative staff become familiar with Word because they have no choice. ...
    (microsoft.public.access.reports)
  • RE: Access user-friendliness needs to improve
    ... responses and generous support offered. ... will prove to be very useful to me and those on my staff who are interested. ... There is no question that developers have done some fantastic work on the ... are some fairly complex databases around that have no VBA at all, ...
    (microsoft.public.access.reports)
  • RE: Access user-friendliness needs to improve
    ... hope of creating jobs within our structure for Access developers. ... are some fairly complex databases around that have no VBA at all, ... Administrative staff become familiar with Word because they have no choice. ...
    (microsoft.public.access.reports)
  • Re: Question about dropping owners permissions...
    ... > create objects owned by the dbo user, and that is what I always recommend. ... >> machine so that developers can create objects within databases, ... >> create databases themselves. ... >> I could easily switch ownership of all objects in the database at the ...
    (microsoft.public.sqlserver.security)