Posted by Erland Sommarskog on 05/17/07 13:08

(mplpost@yahoo.com) writes:
>> I can see two ways out: one is write a signed stored procedure as I
>> discussed in my previous post. The great thing with this is that
>> you can package the database creation into this procedure as well,
>> and thereby the login does not even need dbcreator. The link
>again:http://www.sommarskog.se/grantperm.html.
>
> Will go through the URL in detail. Did u mean that I need to include
> the 'RESTORE DATABASE' command within the stored procedure.

You don't need to. I just suggested that this could be a good idea,
as you then may have to add the xy login to the dbcreator role.

--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

• Next in forum: Re: SqlServer 2005: Importing Data: Idenitity fields getting made into non-identities
• Prev in forum: Re: Optimalization - SELECT tatement
• Thread view: Re: Database Owner cannot connect

[Reply to this message]