all groups > sql server data warehouse > august 2003 >
You're in the

sql server data warehouse

group:

Central Database Design


Central Database Design Shamim
8/11/2003 3:47:13 PM
sql server data warehouse: SQL SERVER 2K

We have 30 databases each for one business units.
Now I am consolidating few tables from 30 databases to one database for
Analysis purpose.

Now my tables in Central db have millions of records.
I need some tips to handle this huge tables for query purpose (already
applied with all Indexes).

Can I go with INDEXED VIEWS ??

Thx
Sh

Re: Central Database Design Kevin Brooks
8/11/2003 4:01:38 PM
Indexed views are only really good for aggregations and joining data from
mutiple tables, is this what you need to do??? Several of our tables are
over a million rows in our production environment and it all comes down to
indexing. Did you create new indexes designed for queries or are they the
existing indexes from the original tables?


[quoted text, click to view]

Re: Central Database Design Shamim
8/11/2003 4:22:37 PM
I am sorry, I meant PARTITIONED VIEWS

Sh

[quoted text, click to view]

Re: Central Database Design Kevin Brooks
8/11/2003 5:07:03 PM
Partition views can help here. You will be able to keep table sizes down
and this can increase query times when done right. It sounds like you moved
multiple tables into one table. If this is the case you will need to break
them back out into smaller tables, add partitioning columns, modify Primary
Keys and build the view. That might be a hassle. I can query a 20million
record table and get a response back in under a second, I just did a query
on 250million and elasped time was 10sec(only one index on there, I know I
could get quicker:)). Did you change indexes for reporting or not?


[quoted text, click to view]

Re: Central Database Design Shamim
8/11/2003 5:13:45 PM
Thanks for the suggestions.

Sh


[quoted text, click to view]

AddThis Social Bookmark Button