Data Warehousing Tip #3 – Build thin slice
My third data warehousing tip is to build thin slice. Deliver subsets of valuable functionality. Get feedback and buy in,...
2019-01-16 (first published: 2019-01-07)
2,837 reads
My third data warehousing tip is to build thin slice. Deliver subsets of valuable functionality. Get feedback and buy in,...
2019-01-16 (first published: 2019-01-07)
2,837 reads
I’ve seen data warehouses that nobody trusts, or are just too complex for end users to report on. Users will...
2018-12-28
1,358 reads
My first data warehousing tip is to store fact data at the leaf level. If you aggregate your fact data...
2018-12-10
316 reads
Part 1 of this series of articles looked at the intricacies of SQL Server transactional replication, and made the observation that the...
2014-10-27 (first published: 2014-10-20)
6,812 reads
The impact of having data sitting in the distribution database that doesn’t need to be there can be significant. The...
2012-11-26
3,988 reads
In this series of blog posts I will looking at issues regarding the size and performance of the distribution database as...
2012-11-08
18,785 reads
By HeyMo0sh
As someone who works in DevOps, I’m always focused on creating systems that are...
By Brian Kelley
I am guilty as charged. The quote was in reference to how people argue...
By Steve Jones
Learn how to tie a bowline knot. Practice in the dark. With one hand....
Hi everyone I asked this earlier but the desired outcome is a bit different...
Hi, I have a SQL Server instance where users connect to via Windows Authentication,...
Comments posted to this topic are about the item Multiple Deployment Processes
I have a query from a former DBA that we run on SQL Server 2025 to check on database metadata. This query references sys.sysaltfiles. I want to refactor this code to be more modern. Which DMV should I reference instead?
See possible answers