From SQL to DAX: Joining Tables

In SQL there are different types of JOIN, available for different goals. This article shows what are the equivalent syntaxes supported in DAX.


From SQL to DAX: IN and EXISTS

The SQL functions IN and EXISTS are useful to implement tests over a set of values. This article describes the corresponding syntax in DAX language.


From SQL to DAX: Grouping Data

The GROUP BY condition of a SQL statement is natively implemented by SUMMARIZE in DAX. This article shows how to use SUMMARIZE and an alternative syntax to group data.


From SQL to DAX: Filtering Data

The WHERE condition of a SQL statement has two alternatives in DAX: FILTER and CALCULATETABLE. In this article we explore the differences between them, providing a few best practices in their use.


VertiPaq vs ColumnStore Comparison


SQL 2012 gives you two different xVelocity engines, with different capabilities and different scenarios of implementation, the paper will help you choose the right one or, at least, raise your curiosity about performing more tests on your specific scenario.


From SQL to DAX: String Comparison

In DAX string comparison requires you more attention than in SQL, for several reasons: DAX doesn’t offer the same set of features you have in SQL, a few text comparison functions in DAX are only case-sensitive and others only case-insensitive, and performance might have a relevant impact in your query


From SQL to DAX: Projection

Using DAX as a query language you will lack a fundamental feature like projection. In fact, DAX allows you add columns to an existing table, but you cannot simply remove some column from a table. In order to do that, you have to use SUMMARIZE, or you can use ADDCOLUMNS