Asp membership database question

[Nathan Laff]

I have a SQL Express 2005 db which a WinForm application connects to.
I've chosen to use the ASP SQL Membership provider to manage application
users and roles.

Currently, I run the aspnet_regsql tool on my existing database. Does it
make sense to create a seperate database just for users and roles? What is
the "best practice" scenario in this case?

Thanks

 

[Nathan Laff]

Oh, also. What is the recommended use of SQL Server authentication when
using the asp membership provider?

Should I "mirror" users created with ASP.NET into my SQL Server users? Or
just create one SQL server user and hard code it into my application for the
database login?

Thanks for any help!