|
|
Posted by mplpost on 05/17/07 12:42
Thanks for your time and suggestions.
> 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.
> The other way is to create the source database with the xy login. Then
> to avoid the login/user mapping problem on the other servers, create
> the login on these servers with same SID as on the source server. This
> is possible with
>
> CREATE LOGIN xy WITH PASSWORD = 'Sehr hemlig!', SID = 0x....
>
> Get the SID on the source server from sys.server_principals. If the login
> already exists on the server, you need to drop it first.
Wow thats a good idea! But the problem is that we already have the
main database already created in the client site. The separate
database creation feature is being included as an enhancement.
Navigation:
[Reply to this message]
|