Yes, that article lead to the solution for SQL 2014 SP1 (though it was only mentioned for SQL 2012 SP2).

I guess in all the roll-ups and fixes included in SP1...