THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Browse by Tags

All Tags » Reporting   (RSS)
  • If a Tree Falls in the Forest, and No One is Around To Hear It…

    You no doubt have heard this old philosophical question that completes with, "Does it Make a Sound?" As nerds, we all know that the answer is that it certainly does make a sound. However, take the question to a more technical place, how much sound does it make, and what is the impact of that sound, is far more interesting, and far more ...
    Posted to Louis Davidson (Weblog) by drsql on January 9, 2017
  • T-SQL Tuesday #005: On Technical Reporting

    Reports. They're supposed to look nice. They're supposed to be a method by which people can get vital information into their heads. And that's obvious, right? So obvious that you're undoubtedly getting ready to close this tab and go find something better to do with your life. ''Why is Adam wasting my time with this garbage?'' Because apparently, ...
    Posted to Adam Machanic (Weblog) by Adam Machanic on April 13, 2010
  • T-SQL Tuesday #005: Reporting

    This month's T-SQL Tuesday is hosted by Aaron Nelson of SQLVariations. Aaron has picked a really fantastic topic: Reporting. Reporting is a lot more than just SSRS. Whether or not you realize it, you deal with all sorts of reports every day. Server up-time reports. Application activity reports. And even DMVs, which as Aaron points out are simply ...
    Posted to Adam Machanic (Weblog) by Adam Machanic on April 5, 2010
  • Mixing OLTP and reporting using indexed views

    I'm not a big fan of denormalizing, nor of repeating redundant redundant information in a database when those facts can already be derived from other information.  A classic example of the latter is when I see questions on newsgroups, forums or StackOverflow that ask how they can update a table's rank column to reflect the current rank based ...
    Posted to Aaron Bertrand (Weblog) by AaronBertrand on December 29, 2009
Privacy Statement