The views expressed herein may not reflect the views of my employer, the Joint Chiefs of Staff, or the Council of Elrond. Fnord.

updates

This is important. To quote Microsoft, “This security update resolves vulnerabilities in Microsoft SQL Server. The most severe vulnerabilities could allow remote code execution if an authenticated attacker runs a specially crafted query that is designed to execute a virtual function from a wrong address, leading to a function call to uninitialized memory. To exploit this vulnerability an attacker would need permissions to create or modify a database.

The security update addresses the vulnerabilities by correcting how SQL Server handles internal function calls and pointer casting. For more information about the vulnerabilities, see the Vulnerability Information section.”

You can download it here. I just finished updating my third and final machine this morning.

Brent Ozar has created a new web site called SQLServerUpdates.com where he maintains the latest CUs and SPs for editions 2005 and later. Very nice one-stop shopping for all your SQL Server update needs!

Apparently it released 11 days ago, I saw it in SQL Server Central’s weekly newsletter. You can get a link to download either the x86 or x64 versions for both the database and ODBC here.

Regarding 2014’s SP1, still no news as to when a new version will see the light of day. But at least we have CU7.

Brent Ozar live-tweeted from yesterday’s Ignite conference keynote speech. Sounds like typical keynote blather: new toys, some of which won’t work, some won’t work like they displayed them, some could be cool. I wasn’t too keen on the announcement of SQL Server 2016, I really wish they’d stop with this new version every other year. I think it will encourage people to look at hanging on to their older versions since the rate of change is beginning to exceed people’s capacity to absorb the new features. Microsoft recently announced end of support for SQL 2005 next year, which means 2008 will be EOL’d in four years. At least the 2014 installation that I’m working on will still be supported when I leave this job.

It was announced as available on 15 April, according to the SQL Release Services blog. The only problem is that the link goes to an error page. *sigh* It’s going to be a while before my project goes to internal alpha release, much less full release, I’m sure they’ll get it fixed soon.