locked
ASPNETDB.MDF RRS feed

  • Question

  • User2096382003 posted

    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 

     

    Tuesday, April 1, 2008 2:21 PM

Answers

  • User-345632295 posted

    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.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 1, 2008 2:48 PM
  • User1564875471 posted

    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

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 1, 2008 2:59 PM

All replies

  • User-345632295 posted

    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.

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 1, 2008 2:48 PM
  • User1564875471 posted

    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

    • Marked as answer by Anonymous Thursday, October 7, 2021 12:00 AM
    Tuesday, April 1, 2008 2:59 PM