Subscribe to Windows IT Pro
January 13, 2011 01:58 PM

Welcome to (SQL Server) 2011

SQL Server Pro
InstantDoc ID #129428
Rating: (15)

A new release of SQL Server is due out this year, and if you follow blogs or tweets or check Microsoft’s SQL Server website, you might have seen mention of the new version, code-named “Denali” (in keeping with the US National Park theme). Unofficial word is that this release will be called SQL Server 2011 when it’s launched.

Many people are getting very excited about the new version, and at PASS Summit 2010 this past November, attendees were clamoring to get their hands on the early release, which is called a Community Technology Preview (CTP) instead of a beta. Although I dutifully accepted the installation DVD along with everyone else, I have yet to find the time to install it. In fact, I was just asked to give a session at a conference in May on new features in Denali, so I guess I better start looking at it.

It always surprises me how excited people get about the new version and how few people actually end up upgrading. Of course, there might be two completely different groups of people involved: those who are excited might be the people who write or teach about SQL Server or make recommendations, and those who are actually responsible for production systems are the people that don’t just jump all over each new release.

Why do you think people get so excited about new releases so early on? I can understand if there’s a specific new feature that you think you really need and you’ve been waiting years for it. For example, user-defined functions were finally added in SQL Server 2000 (Microsoft had been promising the feature since SQL Server 6.5), and there were many people who wanted to make sure they understood exactly how the feature worked as soon as possible. In SQL Server 2005, Microsoft introduced table and index partitioning, and designing and testing a complete partitioning solution was a long and involved process, so many people wanted to be able to get started on it early.

For the Denali release, it’s easier than ever for you to find out what the new features are that you might get really excited about. You can find out about the new features even if you don’t have access to the CTP (or the hardware to install it on) or you just choose not to install it. The documentation is available online and is updated regularly.

Probably one of the best places to start poking around is on the Books Online for SQL Server “Denali” page.  This page points you to the “What’s New” page for each of the product components, including the Database Engine, SQL Server Integration Services, SQL Server Analysis Services, and more.

The page for the new features in the Database Engine, where I’ll be spending most of my time, divides the new engine features into five categories:

  • Availability
  • Manageability
  • Programmability
  • Scalability and Performance
  • Security

Unfortunately, as of this writing, some of these topics, such as Scalability and Performance, are empty. However, the Programmability page notes that Denali will give us the ability to do ad-hoc query paging. What this means, according to the documentation, is that “You can specify a range of rows returned by a SELECT statement based on row offset and row count values that you provide.”

So if this is a capability that you’ve been waiting for, you just might want to get your hands on the Denali CTP to try it out immediately. I’ll admit that this is a very common feature request on the help forums, so it just might be a feature that users are excited about.

Are you excited about Denali? I’d love to hear your reasons why and how much you’re planning to use the Denali CTP releases.

 

Related Content:

ARTICLE TOOLS

Comments
  • Rob Schoedel
    1 year ago
    Jan 31, 2011

    The single feature that has me most intrigued are the new columnstore index type. In the process of developing PowerPivot for SQL 2008 R2, MS conceptualized how to apply the technology more generally. While the main market here is ETL & querying from fact tables, it should radically improve performance for any query where the underlying tables are in a star-schmea pattern. I'm interested to experiment with how broadly the improvements go beyond that.

  • Galvani
    1 year ago
    Jan 19, 2011

    I doubt that there is a single application out there waiting for the new features of a new release to be developed and deployed. In real world, you have to deal with limitations and you use to find out workarounds. The new features are more useful for new applications. That is my experience.

    Take Care!

  • SANTHANAM
    1 year ago
    Jan 16, 2011

    We have a couple of mission critical applications that use SQL Server and our entire DW runs on SQL Server. I would rather wait to jump to SQL Server 2011. In the meantime, I would get my feet wet by "playing" with SQL 2011 before jumping to a conclusion. IMHO, it definitely has come a long way, especially the Relational, ETL and OLAP layers.

  • Rick
    1 year ago
    Jan 14, 2011

    Simple. Like a child looking through the store window, "New Toys!!!" Then they look in their pockets, frown and walk off with their head hanging down. Been there, done that. I can say I was able to get 2008 R2 shortly after it's release. :)

  • Ray Stevens
    1 year ago
    Jan 13, 2011

    I think that you are correct about some of the motivation about new versions. The problem, speaking from frist hand experience, is that it is very interesting to check out the features about a new version and then find it lacking in many ways or troublesome so that you don't want to spend money on a new version that provides a whole new set of problems. So, you wait until it is shaken out which may take years. After a while you don't bother with new versions until they are proven. There are people in all stages of this process so the results of interest are all over the place allowing you to analyze it in many ways. Also, the version cycle time for most implementors is much longer than the release time of the manufacturer due to a conflict in interests and other reasons. It is still fun to look at a new version to see if enough new things are there to warrant the onerous job of making the change. Ray Stevens.

You must log on before posting a comment.

Are you a new visitor? Register Here

advertisement

advertisement

Windows is a trademark of the Microsoft group of companies. Windows IT Pro is used by Penton Media Inc. under license from owner.