sql server - handling big apllications and big databases -


i allready have programmed small applications, database design simple, 1 normalized database containing datas need application.

now want try programm bigger:

there should 4 websites build mvc3. websites should use 1 sql-membership-database , tables contacts , on should shared between diferent pages too.

now question is: how start?

1. should use 1 database tables (each application needs 40 different tables) including shared tables sql-membership-database or should create 1 database shared data, 1 application 1, 1 application 2 , on?

2. should put applications 1 mvc3-application , seperate them using areas?

3. applications need save text , pictures, should use 1 table pictures application 1/2/3... , choose them application id or should create image-table each application (same question texts , descriptions , tooltipps...)?

4. idea work woth blob (ms sql 2008 r2) save files, think choice?

is there have got tipps ore experiances in creating huge (for me huge ;-)) applications this?

lot of , greetings hw

rtfm patterns of enterprise application architecture.

you dont think in mvc o databases thoses implementations should approach in oop , domain model.

although point bad ideas (from personal point view), how

-save images,text files in databases

now number of tables not point work on databases of more of 6000 tables, many views , lot utils point domain model.


Comments

Popular posts from this blog

c# - SharpSVN - How to get the previous revision? -

c++ - Is it possible to compile a VST on linux? -

url - Querystring manipulation of email Address in PHP -