Re: Designing a Reporting Database

From: BP Margolin <bpmargo_at_attglobal.net>
Date: Sat, 21 Jul 2001 23:25:48 GMT
Message-ID: <3b0c393a_4_at_news3.prserv.net>

Todd,

You really have not posted enough information for a meaningful response, IMHO. Perhaps you can provide some additional information:

1. There seems to be a contradiction between "the system contains about 100 tables" and "how to setup the database portion" ... if the tables already exist, what is it you are setting up?
2. Is this system supposed to do both OLTP and DSS / OLAP, or is it strictly DSS / OLAP?
3. If it is both OLTP and DSS / OLAP, is it an option to split the two functions into separate servers, and perhaps have replication of some other process keep them in sync?

Just a comment ... excluding indexed views, well-written views by themselves have no impact on performance. SQL Server takes the view definition and substitutes it into the query before creating a query plan.

4. What version of SQL Server are you using? If it's SQL Server 2000, are you familiar with indexed views?

There are probably a load of other pertinent questions, but these are the first few off the top of my head.

If you respond to this, please don't just answer with Yes / No type responses, but please supply some "meat" also. If you want us to spend time answering, then please spend time providing sufficient background.

---

BP Margolin
Please reply only to the newsgroups.
When posting, inclusion of SQL (CREATE TABLE ..., INSERT ..., etc.) which can be cut and pasted into Query Analyzer is appreciated.

"Todd Rubel" <trubel_at_oakgroup.com> wrote in message news:d272bee7.0105231000.48bf2ea3_at_posting.google.com...
> I need to create several reports for a new system I'm implementing.
> The system contains about 100 tables and I need to create the most
> effecient reporting system possible.
>
> I'm looking for advice on how to setup the database portion of this
> application. I was thinking about using views but I am afraid of the
> inefficiency. Next I was thinking about using separate tables written
> with lots of triggers.
>
> Any advice from projects you've worked on or ideas you've heard would
> be greatly appreciated. Thanks.
Received on Sun Jul 22 2001 - 01:25:48 CEST