|
database
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Separate business database from authentication DB ?Hi Everybody,
I'm developping a commerce Web Site using ASP.Net 2.0 and SQLServer. ASP.Net 2.0 relies on SQL Server to manage authentication, profiles... Should I use a second SQL Server Database to store my business informations distinct from the one used by ASP (aspnetdb.mdf) to handle authentication OR Can I use a single database to handle all the stuff ? What are the 'fors' and 'cons' ? I'd appreciate your expertise... Philippe Hi Philippe,
I would go ahead in having multiple databases, if you have a clear demarkation on what data goes where and have a logical grouping in mind. It doesn't hurt the server (performance wise) to handle multiple databases though there might be a slight overhead in opening mutiple files and accessing it together. Backing up and restoration will take longer time if you have multiple databases, but on the flip side, in case of an issue, you can restore only that particular database. On the whole, I wouldn't mind using multiple databases if the slight adminstrative overhead is not a contraint for you. Hope this helps. Thanks Omnibuzz for kindly this newbee question.
I appreciate, philippe Show quote "Omnibuzz" wrote: > Hi Philippe, > I would go ahead in having multiple databases, if you have a clear > demarkation on what data goes where and have a logical grouping in mind. It > doesn't hurt the server (performance wise) to handle multiple databases > though there might be a slight overhead in opening mutiple files and > accessing it together. > Backing up and restoration will take longer time if you have multiple > databases, but on the flip side, in case of an issue, you can restore only > that particular database. On the whole, I wouldn't mind using multiple > databases if the slight adminstrative overhead is not a contraint for you. > > Hope this helps. > > -- > -Omnibuzz (The SQL GC) > > http://omnibuzz-sql.blogspot.com/ > > |
|||||||||||||||||||||||