2010-02-08
3,046 reads
2010-02-08
3,046 reads
Architecture and data warehousing are not static. From the first notion of a data warehouse to a full-blown analytical processing architecture that includes data marts, ETL, near line storage, exploration warehouses, and other constructs, data warehousing and its associated architecture continue to evolve. In 2008, the book on the latest evolution of data warehousing appeared – DW 2.0: The Architecture for the Next Generation of Data Warehousing (Morgan Kaufman). In that book the general architecture for data warehousing in its highest evolved form appeared.
2010-01-12
4,485 reads
Recently, I was at a conference, and I heard the following discussion about what a data warehouse was. One person suggested that a data warehouse was really all the old legacy systems connected by software that could access the data. By calling such a contraption a data warehouse, the organization could avoid having to do the hard and complex work of integration. There are so many problems with this federated approach to a data warehouse that they are almost not worth repeating here. But (once again!) here goes.
2009-11-09
6,637 reads
Best-practice advice on software vs. coding, where to integrate, how to capture changed data, when to stage data, where to correct data and what latency levels to shoot for.
2009-10-20
4,926 reads
Given that companies spend on average between 7 and 12 percent of their annual budgets on energy – a focus on reducing energy consumption can have significant bottom-line impact
2009-09-30
3,575 reads
This article outlines a more objective and analytical approach to the ETL and data flow architecture selection based on a set of variables with an objective to enhance the reliability of the overall data warehousing solution.
2009-09-29
4,823 reads
Avoiding getting snared in these traps avoids having to spend a lot of money later to fix problems, Gartner says. In addition, EA benefits can be realized faster and the risk of program failure is reduced.
2009-09-23
4,327 reads
This paper defines a reference configuration model (known as SQL Server Fast Track Data Warehouse) and a CPU core-balanced approach to implementing a symmetric multiprocessor (SMP)-based SQL Server data warehouse with proven performance and scalability expectations for sequential I/O data workloads.
2009-09-04
4,268 reads
The employee dimension presents one of the trickier challenges in data warehouse modeling. These five approaches ease the complication of designing and maintaining a 'Reports To' hierarchy for ever-changing reporting relationships and organizational structures.
2009-08-26
3,651 reads
This paper provides an overview and guide to SQL Server® Fast Track Data Warehouse, a new set of reference architectures created for scale-up (SMP) SQL Server based data warehouse solutions. It includes a summary of the resources available in the reference configuration, the distinguishing features of the approach, and the steps necessary to take full advantage of the new architectures.
2009-06-26
4,002 reads
By Arun Sirpal
Do you know what happens when you enable zonal redundancy for your SQL managed...
By Kevin3NF
Why You Shouldn’t Overlook This Quiet but Critical SQL Server Setting If you’ve...
By Steve Jones
The PASS Summit goes on tour this year, with the final date the first...
Comments posted to this topic are about the item How a Legacy Logic Choked...
Make your corporate events more engaging with a fun twist. Our booths capture energetic...
I've written this code, but it is showing right now as 2 rows per...
I have this table in SQL Server 2022:
CREATE TABLE CustomerLarge (CustomerID INT NOT NULL IDENTITY(1, 1) CONSTRAINT CustomerLargePK PRIMARY KEY CLUSTERED , CustomerName VARCHAR(20) , CustomerContactFirstName VARCHAR(40) , CustomerContactLastName VARCHAR(40) , Address VARCHAR(20) , Address2 VARCHAR(20) , City VARCHAR(20) , CountryCode CHAR(3) , Postal VARCHAR(20) ) GOIf I check the columns_updated() function return in a trigger, what is the data returned? See possible answers