Well, as an initial starting point, there are very different considerations when creating an OLTP vs. an OLAP system. OLTP transactions must be able to handle many small, frequent write/updates, whereas in an OLAP system you're doing very large reads whose results could be cached or even written to a permanent table. OLAP schemas are often of the "star" variety; denormalized to just first normal forms sometimes... Creating an OLAP system usually requires the skills of someone who truly understands the business in order to create a correct set of data that is in sync with what kind of information the business is looking for.
Anyhoo, this topic goes on and on, and is extremely deep and broad. Ralph Kimball is the acknowledged expert on the subject; try looking for stuff from him first. ----- Original Message ----- From: Michael Tangorre <[EMAIL PROTECTED]> Date: Wednesday, June 18, 2003 2:51 pm Subject: SQL > I am posting this again as someone replied without leaving the > original message in the reply and now the responses are offbase. > > Anyways, the original question was... > > does anyone have any links or references that will shed some light > on breaking an appliction data structure (sql server database) > down into transactional and reporting/lookup databases to enhance > performance. I am looking for some advantages and disadvantages in > doing so, and maybe some examples... > > Thanks. > > Mike > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Signup for the Fusion Authority news alert and keep up with the latest news in ColdFusion and related topics. http://www.fusionauthority.com/signup.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
