ASPNETDB.MDF

Im using the createuserwizard to set up my registration process and therefore a
database - ASPNETDB.MDF - has automatically been created.

Is it best to then use this same database for all my other website data or am i
fine to use another database for that?

Id initially setup my own database for customer info so now have the 2 databases
so am wondering if there is any benefit to combine them or is ASPNETDB.MDF only
meant for ASP.NET membership info.

thanks

Generally speaking, you can install the membership schema onto your database
containing your application data because 

1) The ASPNET DB is fairly lightweight
2) The table name are very unique and it is unlikely that it will conflict.

mark-1961:Is it best to then use this same database for all my other website
data or am i fine to use another database for that?

it depends on many things, if your application database needs a foreign key from
the membership database , then 

i think you need to create a database for your application , and instead of
using the ASPNET.MDF, you can add  the membership tables to the newly created
database ,

But if your application database doesn't make any relationships with the
Mebership database , then i think its more simple to just use the default
ASPNET.mdf database,

you should also consider the hosting company ! some of the hodting comapnies
prevent you from using the SQL express , 

so i think its easier for deployment (and maintanace ) to have them all in one
Database 

 

to add the Mebership tables to your database , read this :

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

I also  recommened to read this thread : http://forums.asp.net/t/1239807.aspx