Imar I need your help

mark_gilb · August 22nd, 2013, 10:45 PM

I have both beg asp.net 4 and 4.5 but in 4.5 you combined the two databases into one, which is a better approach the coupling or the separation?? Is it about security or what?? Please give me the pros and cons...
Thx

Imar · August 23rd, 2013, 03:57 PM

Hi there,

I usualyl merge them as it will make things a lot easier to manage. In addition, it's easier to join data on the membership tables so you can link other data to members in the database.

In the 4 book I merged the two as well, in Appendix B. However, .NET 4.5, with the new membership providers made this a lot easier, so that's why I discussed it in the book and not in an appendix.

Cheers,

Imar

mark_gilb · August 23rd, 2013, 04:10 PM

Thanks imar

but which approach is more profesional and better for future expansion, and isnt it as easy as uploading two databases instead of one or is it alot of work??

Imar · August 23rd, 2013, 04:16 PM

Like I said, I would merge them as it gives you more control. Neither is more professional than the other, but my merging you have less to worry about (less databases to backup, easier deployment, fewer accounts to manage, and so on). In addition, you get more flexibility as you can more easily join related data.

I would only use a separate membership database if I had multiple web applications using the same membership database. In that case, a dedicated database would make a lot of sense.

Cheers,

Imar