Re: Is this really the best way?
From: Moff (moffnospam@hotmail.com)
Date: 01/23/03
- Next message: Mark Talbot: "SQL Connection using ASP"
- Previous message: R. van Noorloos: "Re: Security bug?"
- In reply to: David Pendleton: "Is this really the best way?"
- Next in thread: David Pendleton: "Re: Is this really the best way?"
- Reply: David Pendleton: "Re: Is this really the best way?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "Moff" <moffnospam@hotmail.com> Date: Thu, 23 Jan 2003 08:48:25 -0000
They could just write CREATE PROCEDURE dbo.MyProc AS ....
"David Pendleton" <qnircra@gpd.arg> wrote in message
news:O6gmi$kwCHA.2504@TK2MSFTNGP10...
> Our SQL developers authenticate via Windows NT.
>
> Each developer is a member of a database role, db_developer. This role has
> been granted CREATE PROCEDURE and FUNCTION and is also a member of
> db_datareader and db_datawriter.
>
> During development, a developer creates an object, in their own schema,
> resulting in something like:
>
> dave.sp_my_procedure
>
> Other developers working in other languages, ASP for example, must qualify
> their stored procedure calls with the same schema.
>
> When the code is migrated to a QA environment, a DBA must change object
> ownership to dbo, and the ASP developers must modify their code once again
> to work with the new schema.
>
> This is tedious, time consuming and is prone to error. Is there a better
> way? Can the db_developer role be granted the ability to create procedures
> as dbo?
>
> Thanks all.
>
> --
> ROT13 my email address to reply
>
>
>
>
>
- Next message: Mark Talbot: "SQL Connection using ASP"
- Previous message: R. van Noorloos: "Re: Security bug?"
- In reply to: David Pendleton: "Is this really the best way?"
- Next in thread: David Pendleton: "Re: Is this really the best way?"
- Reply: David Pendleton: "Re: Is this really the best way?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
