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,983 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,768 reads
By James Serra
I’m honored to be hosting T-SQL Tuesday — edition #192. For those who may...
By Vinay Thakur
Continuing from Day 2 , we learned introduction on Generative AI and Agentic AI,...
Quite the title, so let me set the stage first. You have an Azure...
Comments posted to this topic are about the item A Quick Restore
Comments posted to this topic are about the item Guarding Against SQL Injection at...
I have a quick question on Ola Hallengren Index Optimize Maintenance . Do we...
While doing some testing of an application, I wanted to reset my environment after doing some testing with this code:
USE DNRTest BACKUP DATABASE DNRTest TO DISK = 'dnrtest.bak' GO /* Bunch of stuff tested here */RESTORE DATABASE DNRTest FROM DISK = 'dnrtest.bak' WITH REPLACEWhat happens if this runs, assuming the "bunch of stuff" isn't anything affecting the instance. See possible answers