Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
shenulal
Starting Member
11 Posts |
 Posted - 2012-07-21 : 02:59:53
|
| Hi all, I have an application which works in SaaS model. In that one large number of clients are there and each client have min 1 million record/ month and they can keep their historical data for min 3 months. So, please give me the best option to design this database. I had some few ideas like;1. Keeping seperate database for each client. (not good i think)2. Keep seperate table for each client (also not good practice, i think)Please suggest me your openionregards,Shenu lal |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
shenulal
Starting Member
11 Posts |
Posted - 2012-07-21 : 04:46:14
|
| Hi Tara Kizer, Thank you very much for your suggestion. It's actually for each transaction for each user for a particular client; this problem arouse. I'll explain you my current designAsID PK UserID FK for the user transaction TransTime datetime etc...In this situation with the TransTime i have to use some processing and the clients shall be taking the report for particular interval. While, doing the table partitioning shall i want to do the partition based on UserID or using TransTime? |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
|
|
|
|
|
Database Design for Large no of Records