2010-02-08
3,052 reads
2010-02-08
3,052 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 Ed Elliott
Running tSQLt unit tests is great from Visual Studio but my development workflow...
By James Serra
I remember a meeting where a client’s CEO leaned in and asked me, “So,...
By Brian Kelley
If you want to learn better, pause more in your learning to intentionally review.
By Kanha Booking Wildlife Adventure India
Opting for the perfect Kanha National Park tour package is a necessity for a...
Hello team Can anyone share popular azure SQL DBA certification exam code? and your...
Comments posted to this topic are about the item Faster Data Engineering with Python...
I have this code in SQL Server 2022:
CREATE SCHEMA etl;
GO
CREATE TABLE etl.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT etl.product
VALUES
(2, 'Bee AI Wearable');
GO
CREATE TABLE dbo.product
(
ProductID INT,
ProductName VARCHAR(100)
);
GO
INSERT dbo.product
VALUES
(1, 'Spiral College-ruled Notebook');
GO
CREATE OR ALTER PROCEDURE etl.GettheProduct
AS
BEGIN
exec('SELECT ProductName FROM product;')
END;
GO
exec etl.GettheProduct
When I execute this code as a user whose default schema is dbo and has rights to the tables and proc, what is returned? See possible answers