Business Intelligence

  • Nov 19, 2012

    PowerPivot as Tableau Data Source 2

    I find PowerPivot to be an incredibly powerful tool for building ad-hoc analytical models from heterogeneous data sources. Now, there are a LOT of tools on the market today that can do that. But PowerPivot has the unique position of being fully integrated into Excel, which means that the power to build in-memory analytical models is now very easy and very much now the domain of business and data subject matter experts....More
  • Nov 11, 2012

    Big Data Analytics with Hive, Windows & SQL Server 1

    Big Data has become one of the most over-used and over-loaded terms in IT and data management in recent years. Since we focus on business intelligence for SQL Server in this blog, I think it’s fair to make the statement that many of us have had “big data” data warehouses and analytics in SQL Server for many years....More

Digital Magazine Archives

Browse back issues of SQL Server Pro, from January 2007 through the last issue published in April 2014. Find the back issues here.


From the Blogs
Sep 29, 2015

Data Breaches and Insider Threats

I’ll sound a bit like Captain Obvious for bringing this up, but it’s important to remember that security encompasses a lot more than protecting sensitive data from the specter of outsider threats like hackers. Properly implemented security policies also account for threat-models that include insiders – or people within your organization....More
Sep 15, 2015

Setting Up Additional Checks to Ensure Regular Transaction Log Backups 1

There’s simply no way to overstate the importance of regular Transaction Log Backups. Not only do they help protect from disaster, but regular execution of T-Log backups on Full (and Bulk-Logged) Recovery databases helps keep thing “fit and trim”. Most of the time, setting up a Notification for when T-Log Backup Jobs fail is enough to let you know when something goes wrong....More
Sep 1, 2015

Stop Using INFORMATION_SCHEMA and SysObjects for Exists Checks 3

Code like this isn’t optimal: IF EXISTS(SELECT * FROM sys.objects WHERE name = N'TableToDrop' AND type = 'U')         DROP TABLE TableToDrop; GO Neither is this: IF EXISTS(SELECT TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_NAME = 'TableToDrop')         DROP TABLE TableToDrop; GO Yet, I see both of those used all of the time – over and over again. Even though it’s 2015.  ...More
SQL Server Pro Forums

Get answers to questions, share tips, and engage with the SQL Server community in our Forums.

Sponsored Introduction Continue on to (or wait seconds) ×