Hi,
I am developing an editorial system(MS-SQL). There are a public part(frontend for reader) and an editorial part (backend for editor, admin,...).
The public part of system will be used approximately 1000 acesses/s.
A possible solution:
I solve whether I have to use two databases:
1.DB all data
2.DB with data for frontend
acesses............trigers
--->2.DB <----1.DB
or more of databases or else?
The purpose is, a reader should have good response that the reader don't wait.
Could you give me any advice ?
Thanksone database
make sure all tables are properly indexed for performance of your main queries|||and is there any at least one reason for more database ??|||separate database can be backed up and recovered separately
No comments:
Post a Comment