A few months ago we ran a series of columns dedicated to defining each of the major disciplines of data integration: extract, transformation and load (ETL); enterprise application interchange (EAI); and enterprise information integration (EII). We also asked for input as to which method or methods of integration are in use, or planned to be used, in your organizations.
2005-04-27
1,232 reads
2005-04-20
1,867 reads
2005-04-07
2,200 reads
2005-03-23
2,030 reads
2005-03-16
2,274 reads
2005-03-15
2,208 reads
A mind is a terrible thing to waste and so is the vast quantity of untapped data structure meta information available free for the using in any XML document. This semantic data available in XML is like gold lying on the ground ready to be scooped up and cashed in with little or no effort. This is meta information that can be utilized immediately to significantly increase the value of the raw XML data. By automatically utilizing this valuable structure meta information, hierarchical fourth generation languages (4GLs) can nonprocedurally process XML's complex multi-leg hierarchical structure. This significantly increases the usefulness of the data and makes it immediately available for use at its enhanced value. This article describes the semantics of hierarchical data structures and how they can be automatically utilized by 4GLs.
2005-03-14
1,424 reads
To kick off our first column of the year, we're going to take on a challenging subject that all designers face: how to deal with changing dimensions. Unlike most OLTP systems, a major objective of a data warehouse is to track history. So, accounting for change is one of the analyst's most important responsibilities. A sales force region reassignment is a good example of a business change that may require you to alter the dimensional data warehouse. We'll discuss how to apply the right technique to account for the change historically. Hang on to your hats — this is not an easy topic.
2005-02-21
1,868 reads
November 13, 2004 / Issue TOC
Surrounding the ETL Requirements
Before designing an ETL system, you must first understand all of your business needs.
By Ralph Kimball , Margy Ross
Ideally, the design of your extract, transform, and load (ETL) system begins with one of the toughest challenges: surrounding the requirements. By this we mean gathering in one place all the known requirements, realities, and constraints affecting the ETL system. The list of requirements is pretty overwhelming, but it's essential to lay them on the table before launching a data warehouse project.
The requirements are mostly things you must live with and adapt your system to. Within the framework of your requirements, you'll have many places where you can make your own decisions, exercise your judgment, and leverage your creativity, but the requirements are just what they're named. They are required.
2005-02-15
1,855 reads
This article discusses the challenges of merging unstructured data into BI systems and provides an example of such a merge to solve an organizational problem.
2005-02-03
1,230 reads
By James Serra
There are three Azure SQL products with so many different deployment options, service tiers,...
By Steve Jones
I hosted this month’s T-SQL Tuesday party with my invitation asking about tracking permissions....
By Steve Jones
I was asked to do some a little thinking and brainstorming recently. Rather than...
Hi, Does anyone have experience with MEMORYBROKER_FOR_RESERVE ? when suddenly there is somehow constantly...
I just learned that my database was created on my C:\ drive in the...
I am needing to migrate a MSSQL db to MySQL, on a different server...
I have a complex database with a few filegroups and files. Can I run a backup command like this? (assume file/filegroup names are valid).
BACKUP DATABASE [complex]
FILE = N'thirdone'
, FILE = N'thirdtwo'
, FILEGROUP = N'second'
TO DISK = N'C:\Program Files\Microsoft SQL Server\MSSQL16.SQL2022\MSSQL\Backup\complex.bak'
WITH NOFORMAT, NOINIT, NAME = N'complex-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10
GO
See possible answers