locked
ASP.NET Identity database separate from site's other database? RRS feed

  • Question

  • Hello Experts!

       I and other team were in discussion with Database design solution for and point came out that should keep asp.net Identity stuff in same database or different database? I haven't worked or developed ASP.net. 

    so what are the general best practices should follow? should keep in separate DB on SQl?

    expecting large amount of users ( 25K) within a year. 


    Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit

    Tuesday, September 6, 2016 4:41 PM

Answers

  • expecting large amount of users ( 25K) within a year

    No, that's not a large amount.

    If you don't what to use any foreign key relation to the ASP.NET identity database tables, then it doesn't matter if you have it in a separate database or in the same as the application uses; otherwise use one database for all.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Proposed as answer by Naomi NEditor Tuesday, September 6, 2016 6:16 PM
    • Marked as answer by -kit Wednesday, September 7, 2016 12:45 PM
    Tuesday, September 6, 2016 4:50 PM
    Answerer

All replies

  • expecting large amount of users ( 25K) within a year

    No, that's not a large amount.

    If you don't what to use any foreign key relation to the ASP.NET identity database tables, then it doesn't matter if you have it in a separate database or in the same as the application uses; otherwise use one database for all.


    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    • Proposed as answer by Naomi NEditor Tuesday, September 6, 2016 6:16 PM
    • Marked as answer by -kit Wednesday, September 7, 2016 12:45 PM
    Tuesday, September 6, 2016 4:50 PM
    Answerer
  • Thanks Olaf.

     At this point it's not decided that FK relations ship will be using for the table relations. But you mean FK relations ship to main application tables? 

    we may plan to go for single sign on with FB or google login as well. so any idea what will be best solution as DB point?

    at what point to consider to go for  separate database ? if have large number of users only? 

    Thanks again


    Thank you very much for your time and effort to answer this post. Please Mark As Answer if it is helpful. \\Aim To Inspire Rather to Teach Best -Ankit

    Tuesday, September 6, 2016 8:18 PM
  • Having one database is easier to maintain, and really, even if you may get a few million users it's still not a large amount of user data.

    Olaf Helper

    [ Blog] [ Xing] [ MVP]

    Wednesday, September 7, 2016 7:46 AM
    Answerer