Combine aspnetdb with the applications database

I have tried to find all the threads related to this topic. At this point I would like to find out what the best practices are for doing this.

I plan to use Membership, Roles, and the login controls to handle my authentication and permissions issues. I want to use the same database for my application data as for Application Services, using a standard SQL Server.

So far, the easiest way to set this up that I can think of is to:

1. Use aspnet_regsql.exe to create the Application Services Database schema

2. Edit the "LocalSqlServer" entry in <connectionStrings> to point to the above database

3. Add the tables, views, stored procedures, etc., that I need for my application into the database created in step 1

Is there any more configuration I need to do to get Membership and Roles working? When I did the Walkthrough, step 2 seemed to be the only requirement for getting Membership and Roles to work.

Will I run into any trouble using LocalSqlServer for my application data updates?

I would be interested in any other approaches to setting up a combined database, including opinions why and why not to do it.

There should be no other problem if you've configrue the application to connect to the right database using login which has proper permissions on that database. You cna take a look at Scott's article if you haven't read it yet:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx