LinkedIn | FaceBook | Twitter
Well, it’s the first day of the SQL Connections conference in April of 2008 (yes, on a Sunday, although this will post on Monday) and my booth duties are pretty light. There are some great presenters, among them Kimberly Tripp and Paul Randall, who I think know everything about SQL Server between them. If you don’t read their blog (after mine, of course J) you should.
Anyway, I thought I would start today by talking about the presentation I’m giving here at SQL Connections. Depending on when you read this, the information might be brand-new-not-even-on-your-CTP, or you’re smiling because you’ve been using the features for years. In any case, what I’m presenting on while I’m here are the new manageability features inside SQL Server 2008.
As I’ll mention in my briefing (I’m stealing my own thunder, here) you might notice that a great many of the new features (we call them “improvements”) in SQL Server 2008 have to do with managing the system. That’s on purpose. One of the great strengths of SQL Server is the ease with which you can manage it. I’ve worked on lots of database platforms, and I honestly believe that the tools and features in SQL Server make it the best system to manage. I spoke with a gentleman here at the conference who told me that he manages Oracle, SQL Server and a couple of other platforms, and based on his experience his time is divided only around 15-20% for SQL Server versus Oracle, even though he has more SQL Servers and they are handling more of the production load.
So why focus even more on the management features, if we’re already pretty good at that?
Well, you should never rest – especially if you’re ahead. And not only that, but we keep adding new things to SQL Server that require more and more management. Unfortunately, we can’t raise your company’s headcount, so it looks like you’re the one that has to manage the new stuff. So we have to make that easier and faster.
You’re also facing more consolidation. That might be through more Instances on a bigger system or through Virtual Machines. Yet more things for you to manage.
Also, since SQL Server is moving into the enterprise space, you have more systems to manage overall, whether they are more Instances or more Virtual Machines. So now you have to think about not only looking across multiple systems, but you have less awareness of all the things that are going on with your systems. You need a way to define what you want to happen on each system, and then some way to enforce or at least track when they do or don’t follow your policies.
So the next few blog entries I’ll post are on the things that I’ll talk about in my briefing. I’ll detail each feature that I’ll mention in the briefing, giving you a little background for each.
Keep in mind that I’ll only cover a few of the new improvements. There are lots of Improvements in each area of SQL Server 2008, including management, but I’ll cover the features that fit the needs I’ve just described.
And as promised, here’s a link to the features I’ve discussed today. Since I’ve only mentioned that there are some, get the complete list here: http://msdn2.microsoft.com/en-us/library/bb500435(SQL.100).aspx.
PingBack from http://microsoftnews.askpcdoc.com/?p=3447
Management Studio STILL:
1. prompts me for database connection information when I click "New Query" and have a results window open or an edit window open. It should always open on the same database and connection that whatever window is up, unless of course the person right clicks and tells you which one.
2. Right now it's worse than SQL 2005 because I can't get it to register servers and keep them in the list.
3. I still can't open a query window with the query builder on the top and code below with results below that like the good old SQL 2000 would do. I realize some people like to write this stuff by hand, but man, it's anoying.
Please fix these things.
Good info - can you make sure you post this on the http://Connect.microsoft.com site? That way bugs will get filed and someone will respond to this.