Re: Application Role & 2nd Database
From: Jeff Price (price.9_at_osu.edu)
Date: Wed, 11 Feb 2004 16:00:27 -0500
Thanks, I can run it fine now from Query Analyzer, but not my app... more
work to do there.
I had to set the DB owners as the same account and a few other tasks. The
following MSDN article helped:
"Dan Guzman" <email@example.com> wrote in message
> Creating referencing views will work fine. If you don't want to grant
> permissions on the underlying tables to guest or public, you can use an
> unbroken cross-database ownership chain so that the app role needs only
> permissions on views in the application role database.
> To maintain an unbroken chain, the owners of the objects involved need to
> map to the same login. If your objects are owned by 'dbo', this
> necessitates that the owners of both databases be the same. Also, the
> cross-database chaining option (introduced in SQL 2000 SP3) needs to be
> enabled for those databases.
> Hope this helps.
> Dan Guzman
> SQL Server MVP
> "Jeff Price" <firstname.lastname@example.org> wrote in message
> > I'm trying to use application roles for the 1st time and have a problem.
> > Most of the select statements I use reference tables in a separate
> > After reading the BOL I find that this only works through the GUEST
> > Drat!
> > Any suggestions to fix this? I'm considering setting up views in the
> > DB, but this will involve changing the code and creating the views and I
> > still don't know if it will work.
> > --
> > Jeffrey R. Price
> > Database Manager
> > Computing & Communication Services
> > Max M. Fisher College of Business
> > The Ohio State University
> > 320F Mason Hall
> > 250 W. Woodruff Avenue
> > Columbus, OH 43210-1309