Since the introduction of SQL Azure, there has been some confusion about how it should be used. Some think that the primary goal for SQL Azure is simply “SQL Server Somewhere Else”. They evaluate a multi-terabyte database in their current environment, along with the maintenance, backups, disaster recovery and more and try to apply those patterns to SQL Azure. SQL Azure, however, has another set of use-cases that are very compelling.

What SQL Azure represents is a change in how you consider your options for a solution. It allows you to think about adding a relational storage engine to an application where the storage needs are below 50 gigabytes (although you could federate databases to get larger than that – stay tuned for a post on that process) that needs to be accessible from web locations, or to be used as a web service accessible from Windows Azure or other cloud provider programs. That’s one solution pattern.

Another pattern is a “start there, come here” solution. In this case, you want to rapidly create and deploy a relational database for an application using someone else’s hardware. SQL Azure lets you spin up an instance that is available worldwide in a matter of minutes with a simple credit-card transaction. Once the application is up, the usage monitoring is quite simple – you get a bill at the end of the month with a list of what you’ve used. From there, you can re-deploy the application locally, based on the usage pattern, to the “right” server. This gives your organization a “tower of Hanoi” approach for systems architecture.

There’s also a “here and there” approach. This means that you can place the initial set of data in SQL Azure, and use Sync Services or other replication mechanisms to roll off a window of data to a local store, using the larger storage capabilities for maintenance, backups, and reporting, while leveraging the web for distribution and access. This protects the local store of data from the web while providing the largest access footprint for the data you want to provide.

These are only a few of the options you have – and they are only that, options. SQL Azure isn’t meant to replace a large on-premise solution, and the future for SQL Server installations remains firm. This is another way of providing your organization the application data they need.

There are some valid questions about a “cloud” offering like SQL Azure. Some of these include things like security, performance, disaster recovery and bringing data back in-house should you ever decide to do that. In future posts here I’ll address each of these so that you can feel comfortable in your choice. I’ve found that the more you know about a technical solution, the better your design will be. It’s like cooking with more ingredients rather than the same two or three items you’re used to.

It's here!  The latest version of SQL Server is out, and it's a big release. This is an exciting time for us - this release is an "R2" - a first for SQL Server. No, it isn't a service pack, and no, we didn't change the product so much that it affects anything that you've already installed in SQL Server 2008. You're still able to upgrade from SQL Server 2000 and higher, you get all of the benefits of moving from an earlier platform. Why this kind of timing and naming for the product? And what is different in this release than in SQL Server 2008? And Good questions all.

First, the reason for the release schedule was to properly align Microsoft's flagship database product with Microsoft Office, and with Microsoft's "cloud" strategy. One of the strengths of the SQL Server platform is that it works well with our other products, and in Microsoft Office 2010 and the latest release of SharePoint we have included amazing array of Business Intelligence features for the "non-IT" worker. This means your business users can get at the data they need and want, and the IT department can still control and protect the data the way it should be. It's the best of all worlds.

But it doesn't stop there. As you may have heard, Microsoft is "all in", with a comprehensive cloud strategy.  We have not only a complete cloud development platform (Azure) but also a relational database offering (SQL Azure) that goes beyond just hosting a SQL Server Instance in a rack somewhere. SQL Server 2008 R2 allows you to connect to SQL Azure like you're connecting to a local server. You now have capacity on demand, without losing any of your local systems or control.

And there's more - this release also includes the "Datacenter" edition, with support for up to 256 logical processors, data and backup compression (from SQL Server 2008) and the ability to use SQL Server with "Live Migration" - a virtualization technology that lets you move virtualized servers without downtime. These features, along with rapid adoption in the most mission-critical, enterprise-class environments means that you should consider SQL Server as a "Tier 1" application platform.

These are indeed exciting times for the data professional. Make sure you hit these links to learn more - your organization is counting on you as the data professional to know what's new and useful in the data world. You can also post any questions you have on this post - I'll try and make sure someone gets back with you:

SQL Server 2008 R2 Launch Site: http://www.sqlserverlaunch.com/

Official Microsoft Site for SQL Server 2008 R2: http://www.microsoft.com/sqlserver/2008/en/us/R2.aspx

Hello, I'm Buck Woody - Microsoft's "Real World DBA". I go by that title not because I'm a DBA here (we do have a lot of those, though) but because for over 25 years I've worked as a Data Professional. I've worked at organizations from NASA facilities to hospitals, and from legal offices to manufacturing firms and software development companies. I've been a DBA, a data developer, and a database consultant on everything from mainframes running COBOL flat-file databases to microcomputers running Oracle, DB/2, Sybase, SQL Server, Postgres and Ingres. I've written a few books on SQL Server, been a SQL Server Most Valuable Professional (MVP) and I've run several user groups over the years.

I joined Microsoft just a few years ago and since that time I've worked on the product team as a Program Manager working on the SQL Server 2008 product, and I now work as a Senior Technical Specialist on SQL Server, helping our clients figure out where the SQL Server product fits in their architecture. I also teach a database design course at the University of Washington, and I still volunteer as a DBA so that I keep my hands in the tools and the trade.

From time to time I'll post information here that is different from my daily blogs and weekly articles - but like those posts I'll always make sure that the information has "real world" value. Functions and features are great, but they have to *do something* meaningful before I get excited about them. When I do, you'll be the first to hear it!

I think I may have set myself an all-but-impossible task: to choose ten bloggers who write about SQL Server, and who have been outstanding in the last year. Nearly impossible, not because I can't find ten, but because there are so many more worthy of recognition.  In addition, many of those I will not be including are friends and colleagues, so the task may be as thankless as it is difficult.

Nevertheless, having set myself the goal, I may as well get on with it. My method was simple enough. I started with those blogs I subscribe to, and, of those, found the ones I bookmark most often. These were neatly objective measures, but I was still left with about 20 blogs to consider. Then I had to find some more subjective criteria: are the blogs helpful, insightful, original, well written, newsworthy, and so on. I excluded official Microsoft blogs, focusing instead on the community blogs, so there is only one Microsoft team member on the list.

Here then are My Top 10 for this last year. To be fair to the others who so narrowly missed out, I'll publish a longer blogroll later of those who I consider to be essential reading. For now, let me know what you think of my top ten, in strictly alphabetical order.

Bob Beauchemin
http://www.sqlskills.com/BLOGS/BOBB/
Like most of the bloggers in this top ten, Bob is an active and excellent speaker and writer. Bob is notably excellent when writing about data access and programmability, areas which require both sound understanding of the database technology and the ability to work with, and explain, the latest programming models. If you're an application developer working with SQL Server, then Bob is essential reading ... and don't miss his conference sessions either!

Rob Collie
http://powerpivotpro.com/
Rob is the only Microsoft employee on My Top 10 list because his blog is really very independent and hosted with a quite separate presence and identity. Rob has set out to create a compelling blog for the new PowerPivot product and he does a great job synthesizing his years of experience in the Excel world with his detailed knowledge of the PowerPivot technology. Even better, Rob presents compelling, easy-to-understand scenarios with a great sense of humor. If you're interested in PowerPivot, you need to follow this blog.

Kasper de Jonge
http://business-intelligence.kdejonge.net/
This blog has been a revelation to me this year. Kasper works in the Netherlands and blogs on BI topics. One outstanding feature of his blog is his use of copious screenshots. Often, with a new product just out in public like PowerPivot or the new Report Builder, Kasper sedulously records his experience with setup and first impressions, all captured with useful screens and comments. Even I learn stuff about setting up our BI products here! It's not just about installation either: Kasper explores many new features with the same careful approach.

Andy Leonard
http://sqlblog.com/blogs/andy_leonard/default.aspx
I really enjoy Andy's blog, not just for the technical posts (especially about SSIS), but for the way he writes with a perceptiveness and passion about the community of SQL users. Andy persuades, cajoles and encourages SQL Server users to get out and be part of something bigger: whether blogging, or simply attending a conference or event. Even better, Andy is always very clear about how community support fits in to an often challenging and difficult career path. 

Sean McCown
http://www.infoworld.com/blogs/sean-mccown
Now this is a kick-ass blog. In fact, often times you get the impression that Sean's key motivation in sitting down to blog for the day is just to kick some ass. But he chooses his victims well! Whether it is Microsoft's product teams, officious auditors, or even himself (for delivering a bad presentation), Sean is typically forthright and on target. Sean is also, like Andy Leonard, excellent at supporting DBAs in their career and personal development, with advice in the last year on technical skills, interview techniques and even office politics!

Adam Machanic
http://sqlblog.com/blogs/adam_machanic/default.aspx
The sheer breadth and depth of Adam's posts are testaments to his knowledge of SQL Server. I have only two things to say: read this blog, and try every code sample Adam posts. You'll be better for it.

Paul Randal
http://www.sqlskills.com/BLOGS/paul/
Paul is a former Microsoftie who often draws on his detailed understanding of the relational engine's internals to give unique insights on his blog. As an expert on DBCC, this blog is simply essential reading if you are interested in recovery or repair  - it's title is, in fact,"In Recovery." Even better, if you want to avoid recovery and repair, you need to read this. Paul also writes very entertainingly, which really helps with the often deeply technical matter.

Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson/
Jamie's previous blog used to be called "SSIS Junkie." I don't think he has quite kicked the habit, as his technical posts about SSIS are always excellent, but there is certainly a wider range of interests on display here from data warehousing to SQL Azure.

Kimberly Tripp
http://www.sqlskills.com/blogs/kimberly/
Kimberly is inimitable, both on stage and in her blog. I wouldn't know where to start recommending her work - and if I started I could hardly stop. Let me take one example. Want to know about indexing? Read this blog - for the examples, the technical detail, the good humour, and the sheer practicality of the advice. And that's only one topic. Read the blog, every post.

Chris Webb
http://cwebbbi.spaces.live.com/
Chris is an OLAP guy, and if you know OLAP (whether in the form of SQL Server Analysis Services or any other vendor) you really should subscribe to Chris's blog for its breadth. For those specifically in the SQL Server sphere, Chris's posts on the MDX query language, and more recently on the use of PowerPivot DAX, are not only practical and perceptive, but help to stretch your skills and cover challenging scenarios.

So that's the list. What do you think? Anyone I missed out that you feel really needs to be there? And if so, who would you remove? I'd be fascinated to hear from you.

A few countries around the world have a day set aside for giving thanks - and some do it all year long. We stop to give thanks to those who have made us what we are, and those in the past and present who have given us the benefits that we enjoy. From teachers to family, we owe them a lot.

I've noticed that several technology specialists, especially those that work with SQL Server, go even further. They practice "Active Thankfulness", where they donate their own time, money and effort to give back to the community. The Professional Association of SQL Server, or PASS, is staffed with volunteers, and at the recent PASS conference you could see this spirit of giving all over the event. People lent a helping hand to setting up, organizing and staffing many different activities, including those to help folks with their SQL Server questions. Microsoft donated the entire Customer Advisory Team (CAT) to the event, answering questions and delving deep into technical issues for free. Many of the SQL Server product team members came over to staff the "Ask the Experts" area, and other database professionals gave of their time to handle the "Birds of a Feather" tables - again, all free, all volunteer.

And then there were the SQL Server "Most Valuable Professionals", or MVP's, that donated not only their time but an amazing amount of effort to create a huge book called "Deep Dives", with all of the chapters and even the production costs donated. The money raised by this book go straight to "War Child International", a charity that aids children whose lives have been devastated by war. In the introduction, the MVP's explain that the impetus for this book was a response to Bill Gate's challenge to "do philanthropy where you are." And that's good advice - each of us has learned from someone, whether that's a college teacher or from a data professional that took the time to show us the ropes. You might not be able to find that person, but you can pay it forward by helping someone else. It can be volunteering at a SQL Saturday event, helping out at your local user group, or volunteering your time to help a charity with their technology needs. When you practice this kind of active thankfulness, you'll find the rewards far outweigh the level of work you put in.