SQL Server 2008: Design table structures

Are you talking about installing sql server reporting services where you can design reports to get the data you want from the data stored in the database.

Well for that we will be required complete information that how your source tables holding data and what you required to show in report...

But one suggestion can be ...
You are running your process over night so do every calculation with each permutation & combination and store them in a flat table...
In morning Report will required only to fetch and show that data...

And for the key you can define as per your permutation ...

Hi Saurv,

Yes, it will be nightly process and in the morning on fetch. You caught correctly.

You may take same example aforesaid for department and salary. Kindly let me know in case you need more information.

Best Regards,
Mohit Pandit

Hi,

I've done it myself. I stored the combination in separate table let's say 'LookUp' along with 'Internal_Id' and in another table I store a key with combination in another table.

For e.g. first, I've only three values in two dropdownlist as below:
Note: we will be having default value "Select All" so that means 4 values instead of 3 in dropdown.

Department      Salary
HR (1)      0 to 10000 (1)
Sales (2)      10001 to 20000 (2)
Market (3)      20001 Above (3)

So, second, below table of combinations (as lookup):
As you can see 9 combination because we will be having other value "Select All" and NULL values shows user select all
Internal_Id      Department      Salary
1      1      1
2      1      2
3      1      3
4      2      1
5      2      2
6      2      3
7      3      1
8      3      2
9      3      3
10      NULL      1
11      NULL      2
12      NULL      3
13      1      NULL
14      2      NULL
15      3      NULL
16      NULL      NULL


and third, the Internal_Id column will be used to store actual result values in other result table.
Like I aforesaid 2nd point, all combination key value from 1 to 16 and it will also be having combination like 1,2 (if end user selects department = 1 and salary = 1 and 2) then internal id will match for two rows and internal id will be 1 & 2. So, it will be store in comma separated with in result table.

Now, one challenge seems, the comma separated key combination of internal_id column.

Could you please look into it and give your great thoughts?

Best Regards,
Mohit Pandit

thanks for this.