Cowboy
Thu Mar 13 22:59:55 CDT 2008
Yes. No.
If you want a shared membership, then your scenario is fine. If you are
donig this for a single app, run the membership script against the database
for your app and then you can actually add referential integrity to the
ASP.NET tables.
--
Gregory A. Beamer
MVP, MCP: +I, SE, SD, DBA
Subscribe to my blog
http://gregorybeamer.spaces.live.com/lists/feed.rss
*************************************************
| Think outside the box!
|
*************************************************
"Bogdan" <bogdan@domain.com> wrote in message
news:%23B2PgZYhIHA.3352@TK2MSFTNGP04.phx.gbl...
> Hi,
>
> I'd like to take a full advantage of built-in membership services and use
> aspnetdb's UserId in my app's database. For example, I'd like to
> establish some relationships between membership users from aspnetdb and
> rows in tables in my database. My app would be responsible for enforcing
> the cross-database 'referential integrity'. Does this sound as a
> good/acceptable practice?
>
> Thanks,
> Bogdan
>
>