September 10, 2009 at 9:30 am
Hi,
We have a database/application solution that requires dbcreator rights as it creates a temporary database that is then copied elsewhere, and then the original is dropped. Having the vendor rethink this methodology is out of the question. We have previously used a separate instance for this, but the databases are small and there is almost no activity, so it is a great candidate for consolidated farm solution, except for the CREATE/DROP database requirement.
Is there any way to set up permissions so that this database would play with others? I was thinking of limiting the permissions to an application role, but I would love to hear if any others have encountered this and how they addressed it.
Thanks,
Jeff Bennett
Saint Louis, MO
September 17, 2009 at 9:03 am
crickets. It is so quiet I can hear crickets.
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply