Questions about ASPNETDB.MDF

ibmkahm · October 24th, 2010, 11:37 AM

hello everybody,

in my web site i have two databases, ASPNETDB.MDF and a self created one (database.mdf). (The don't contain a lot of data yet)
But i need a relationship (foreign key) between a table in ASPNETDB.MDF and a table in database.mdf.

So i guess i need to merge both databases first, would you just extend the "ASPNETDB.MDF" with the tables from "database.mdf" ?
or better configure "database.mdf" for the asp.net Applicatoin Services and then delete "ASPNETDB.MDF" ?
Is "ASPNETDB.MDF" even meant to be used in a production online web application?

(Right now i'm using sql server express but i will probably use sql server when deploying Site to a shared host)

thanks a lot for answers

Imar · October 24th, 2010, 12:26 PM

Hi there,

I think this may help: http://weblogs.asp.net/scottgu/archi...25/423703.aspx

Cheers,

Imar

ibmkahm · October 25th, 2010, 04:01 AM

Thanks for the link Imar,

so you would recommend to configure my self created database (database.mdf) for the asp.net Applicatoin Services and then delete "ASPNETDB.MDF" right ??
extending ASPNETDB.MDF is not a good idea ?

Imar · October 25th, 2010, 05:23 AM

The net result is the same: both the required ASP.NET stuff and your own stuff end up in the same database. Whether you add ASP.NET features to your database, or your features to an ASP.NET enabled database doesn't really matter; the resulting database is the same.

However, I prefer to name my databases differently from the default name. I could be working on a number of sites at the same time, and if all databases have the same name of ASPNETDB.MDF, things can get confusing pretty quickly. That's why I prefer to add ASP.NET features to an existing database.

And yes, you can delete the old ASPNETDB.MDF database after you ran aspnet_regsql. Just be aware that no data migration takes place.

Cheers,

Imar