Featured Article(s)
Archiving Your Database (The technical Side)
Once the data has been identified, you can start looking at the multiple ways to actually archive the data. There are a number of ways that you can accomplish this. This article will outline how I have done archiving in the past.
SQL Server 2010^H^H 08 R2
Strange things happening with SQL Server. The keynote on Monday from TechEd talked about a fairly significant shift in SQL Server releases. The talk was of SQL Server 2008 R2 – Kilimanjaro. What? You thought Kilimanjaro was SQL Server 2010? Well, if you Google it, you’ll see that many others think the same, and in fact there are announcements from very significant sources over the last few months talking about SQL Server 2010.
So the information now is that there is no SQL Server 2010. "Never was." That the BI and self-service tools that were part of the release were actually the R2 release. That "Kilimanjaro" always referred to R2. The next full release of SQL Server will follow the R2 release by about 24-36 months. You can expect to see full release of R2 in the first half of next year – CTPs should follow later this year for testing.
That’s not, of course, what I’ve heard prior to this, and it smells fishy to me, frankly. I’m not trying to make a big conspiracy out of a name change and release strategy change. But I do wonder now what’s behind it. Why the change in releases?
My guess is that adding the leverage to SQL Server to allow for enhanced/easier decision making (BI) and analysis (the self-service stuff) became paramount with the slowing economy. Helping people "do more with less" has become critical and getting that release out to the world is the priority. BUT, if you name it SQL Server 2010, you face the uphill "upgrade" battle at shops. If you can show that it’s an add-on release (R2) the work to roll-out is less severe and could lead to faster adoption of the new release. It’s something like the reporting services add-on strategy was.
I just wish the information flow was more straight-up and didn’t pretend that things hadn’t changed.
If I’m wrong, you know I’ll own up to it – but I’ve spent the better part of today looking to see where things were goofy in my head. Lots of research, talking to different people and even clarifying with Microsoft. I’m pretty sure I have this one right at this point. No SQL Server 2010. Kilimanjaro refers to SQL Server 2008 R2, due out 1st half of next year. It includes BI and AS tools and enhancements (likely some Office tools to support those too, in my opinion only).
I’ll keep you posted.
Watch the Latest SQL Server Show
Interview show – Christopher Regan, Donald Belcham, John Welch on the show today. Tips, best practices, pet peeves, things encountered in the field and a lot more.
[Watch the Show]
Previously:
[Watch] Herve Roggero, Jason Strate, and TJ Belt
[Watch] Tim Heuer, Lynn Langit and Thomas LaRock.
[Watch] Brian Knight, Matt Masson and Shannon Bray.
Featured White Paper(s)
SQL Server Fragmentation Explained
This technical white paper will help you understand SQL Server fragmentation and the performance benefits you can gain on yo… (read more)