Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Question about Data Warehousing
- Thread starter Zamm
- Start date
Zamm
Data warehousing is more of a concept that a type of application. In broad terms, you load archived data into a separate database, often used for reporting or analytical processing. The difference is that many of the table relationships are 'de-normalized', ie you might store a customer's main address in the customer table, instead of in a normalized way, where the address would be in an Address table, where the customer might have many addresses. In addition, many totals fields, ie. are added to tables as 'redundant' fields, ie Order total wouldn't be calculated by reading all detail records, it would have it's own field in the order header. Since the data is static, these types of redundancies are always accurate and you don't need all sorts of triggers and update programs to keep them in sync as you would in an live transaction processing database.
This serves to make the reports run faster, since fewer tables are read to get the data needed, and also it allows management to have an easier time writing their own reports, since they don't need to know all the intricacies of joining tables.
This is only a very surface level look at it, but there is a Data Warehousing forum here.
Oh, and Access can be used for data warehousing, in fact I'm using it as an interem solution for a client right now--with about 10 .mdb files all stretched to close to the 1gig max, some containing just a single table. (This until the client waits for Oracle to drop prices!)
--Jim
Data warehousing is more of a concept that a type of application. In broad terms, you load archived data into a separate database, often used for reporting or analytical processing. The difference is that many of the table relationships are 'de-normalized', ie you might store a customer's main address in the customer table, instead of in a normalized way, where the address would be in an Address table, where the customer might have many addresses. In addition, many totals fields, ie. are added to tables as 'redundant' fields, ie Order total wouldn't be calculated by reading all detail records, it would have it's own field in the order header. Since the data is static, these types of redundancies are always accurate and you don't need all sorts of triggers and update programs to keep them in sync as you would in an live transaction processing database.
This serves to make the reports run faster, since fewer tables are read to get the data needed, and also it allows management to have an easier time writing their own reports, since they don't need to know all the intricacies of joining tables.
This is only a very surface level look at it, but there is a Data Warehousing forum here.
Oh, and Access can be used for data warehousing, in fact I'm using it as an interem solution for a client right now--with about 10 .mdb files all stretched to close to the 1gig max, some containing just a single table. (This until the client waits for Oracle to drop prices!)
--Jim
- Thread starter
- #3
Zamm,
Sorry, I can't think of any books on DW in general offhand, nor any websites specific to Access as a datawarehouse tool. There probably aren't many sites about DW specific to Access, since typically you'll want to use a true dbms, such as DB2 or Oracle. SQL7 I'm sure is used for this, but as far as I know it hasn't reached the 'industrial strength' category of DB2 or Oracle.
There is a DW forum here at Tek-Tips, and one of the experts there might be able to point you in the right direction.
--Jim
Sorry, I can't think of any books on DW in general offhand, nor any websites specific to Access as a datawarehouse tool. There probably aren't many sites about DW specific to Access, since typically you'll want to use a true dbms, such as DB2 or Oracle. SQL7 I'm sure is used for this, but as far as I know it hasn't reached the 'industrial strength' category of DB2 or Oracle.
There is a DW forum here at Tek-Tips, and one of the experts there might be able to point you in the right direction.
--Jim
- Status
Similar threads
- Locked
- Question
- Locked
- Question