Video games are based on rules. To quote my man Morpheus, “what you must learn is that these rules are no different than the rules of a computer system. Some of them can be bent. Others can be broken.” The more that a game attempts to give you, the more variables are introduced, and the greater the scope for bugs and other general weirdness.

I ran into a rather strange situation recently while attempting to set up some new calculated measures in an SSAS cube. I’m still new to MDX, so I ended up chasing my tail around for a while (and crying out for help on both StackOverflow and MSDN) before I eventually tracked down the culprit and solved the issue. Basically, I was trying to create a calculated measure, which, using a couple of date attributes from one dimension, would apply to my [Time] dimension and filter the value of a specified measure to match. Not hard, right?

Being a huge fan of the Tom Clancy games ever since the original Rainbow Six broke onto PC way back in 1998, I picked up Ghost Recon: Future Soldier for the Xbox 360 at the weekend. True to form for the series, the game’s mix of 3rd-person shooting, high-tech equipment and squad mechanics is as entertaining as ever. However, on the back on numerous complaints about audio issues with the game, I’ve encountered this one which has left me, quite literally, speechless.

The 2012 version of SQL Server has brought with it a number of new features, not least the new, Visual Studio 2010 shell-based Management Studio. However, the changes are more than just aesthetic, as I found out when I came to try and upgrade some SQL Server Integration Studio (SSIS) packages from SQL server 2008 to 2012. Most packages upgraded fine, but there were some issues when I tried to upgrade any packages that used Script Tasks containing references to external DLLs.

I was editing some pre-existing SQL Server Agent jobs the other day, adding some interconnectivity and changing steps around as I’ve done hundreds of times before.  These job steps are used to execute SSIS packages (SQL Server Integration Services) on the server and have been running for months (years?) without fail.  However, after I made my changes they started failing on the steps I had edited, throwing the bizarre error:

Option "/CALLERINFO" is not valid.  The command line parameters are invalid.

In my free time lately I’ve been getting into the superb online multi-player in EA and DICE’s Call of Duty baiter, Battlefield 3 on Xbox 360.  For anyone who’s not tried the series, it’s a large scale multi-player military shooter with wide open maps and a variety of land, sea and air vehicles with which to play.  While it’s enormous fun, especially if your fellow players work as a team it’s unfortunately riddled with game-breaking bugs.  Some players seem worse affected than others and the issues seem to be spread across all three of the game’s platforms; Playstation 3, Xbox 360 and PC.