I’ve been continuing with my Data Tales series up at sqlmag.com.
This time I’ve written about a pet hate: seeing code that counts rows when all it needs to do is to check for existence. However, all is not as bad as it seems because the optimizer does a pretty good job of protecting us from ourselves. (At least the SQL Server optimizer does )
It’s here: http://sqlmag.com/sql-server/data-tales-10-it-s-matter-existence
That Power Query webinar that I’m doing for the global Power BI team is on this week.
Love to see you attend.
Registration is here: https://info.microsoft.com/CO-PowerBI-WBNR-FY17-08Aug-25-PowerQuery-PowerBI-Registration.html
I’ve been writing articles for SQL Server Magazine as part of my Data Tales series.
Over the last couple of months, I’ve been writing a min-series about a database on a diet.
Earlier parts described the need for size reduction, how ROW and PAGE compression come into play, how to choose between them, etc.
Part 4 (the final part) is now online here:
It covers GZIP compression of large string fields, PDF size reduction in BLOBS, and more.
Want to get your head around Power Query in both Excel and Power BI Desktop?
I've got a webinar happening for the Power BI team later this month: https://info.microsoft.com/CO-PowerBI-WBNR-FY17-08Aug-25-PowerQuery-PowerBI-Registration.html
The link below is to quite a fascinating article that on the surface is about why Uber moved to MySQL from PostgreSQL.
What it really is about is a severe limitation in how PostgreSQL indexes are updated.
With SQL Server, if you update a few columns in a row, only the indexes that have that column are updated. In PostgreSQL, all indexes still need to be updated. I understand why they've done that but it's not a good outcome.
SQL Server shines in this regard.