Author: Felipe Ferreira

Felipe Ferreira, Pythian Database Expert and Microsoft MVP, explains how embracing the cloud as an emerging technology doesn’t necessarily mean the end of the DBA role.

Felipe Ferreira, Pythian Database Consultant and Microsoft MVP, discusses a shift in the Cumulative Update message sent by Microsoft. See more at: https://blog.pythian.com/sql-server-cumulative-update-changes/

In the last months I’ve been keeping an eye on the Power BI Preview, the new version of the Power BI cloud solution that was completely revamped compared to the first Power BI v1. This last Friday, July 24th, Power BI…

Hey folks, Microsoft released the 5th Cummulative Update for SQL Server 2012 SP2. This update package contains fixes for 27 different issues, distributed as follows:     One very important issue that was fixed on this CU release was KB3038943 –   Error 4360…

Hello everyone, Just a quick note to let you know that this week, while most of North America was enjoying a break, Microsoft released the 6th cumulative update for SQL Server 2014. This update contains fixes for 64 different issues,…

Have you ever needed to start a new data analysis project or create a report for the business users querying a database you never worked before? Or simply know the data distribution of a database to create better indexing strategies?…

During the Worldwide Partner Conference (WPC) that happened last month, Microsoft made public some of the new functionalities that we can expect to see soon on Microsoft PowerBI. If you were on another planet in the last few months, and…

Howdy everyone, Just a quick tip for everyone that is struggling to configure SharePoint Server 2013 PerformancePoint  to connect to a SQL Analysis Services 2012 or 2014 cube. After a new SharePoint Server 2013 installation, I have tried to create…

Howdy everyone, One of the most frequent error messages I come across when dealing with SQL Server, particularly SQL Server 2008 R2, is Error 18056, Severity: 20, State: 29. Not only do I constantly see this error message in the SQL logs,…