Hi Michael,

>Restoring the database is not something that is usually handled through an application, IMO. Most DBAs will fire-up SEM and work through it.
>

I agree, but this is an MSDE-based "lite" version of our flagship product, and a requirement is to close off all external access to the database. Customers wanting more access with the full SQL Server will have to upgrade.

>With that said, what about having a second, administrative application that doesn't have to go through the application role?
>

I guess I could use the "sa" account for this operation, as it sounds like I won't be able to get it working with the application role. Thanks for the idea.

>-Mike
>
>>A requirement for our app is to have access to the SQL Server database only through the application. I think an Application Role is the ticket for that. I set up a guest account for authentication with no permissions. The application role gives the app access to everything else, and that seems to work well, except when trying to restore a database. The problem is that the restore command wants exclusive access to the database. I tried the USE command to switch database contexts, but that is not allowed while an application role is active. If I don't use the application role, then I don't have the necessary permissions to perform the restore. Any ideas?
>>
>>Thanks.