For the inaugural SQL Rally in Florida last year I wrote a blog post urging men to attend the Women in Technology (WIT) luncheon. I wanted to express my opinon that it wasn’t for women only and that it was important for men to be part of the discussion about the issues women face in the tech world. Today at SQL Rally in Dallas there is a WIT session and the post I wrote last year, Why the Women in Technology thing matters…to Men, still applies. Read it to learn why it’s important for you to participate in the conversation.
The panel will discuss the topic When and How to Negotiate which should draw a lot of interesting comments and feedback. I’ll see you there!
I’m headed to Dallas for SQL Rally this afternoon from Colorado and I’m really looking forward to it, not just because I’m going to present a session on Columnstore Indexing, but because of everything else I get to do. I’m one of those people who over the years has had to learn how to attend a conference and get as much out of it as possible, and I think I’ve finally got it down.
Little Sleep, No TV
Even though I’ll be there a little more than 48 hours, my schedule is already packed. I’m going to the speaker reception tonight, the social networking over coffee Friday morning, I’ll stop by the karaoke Thursday night (but not sing), and I’ll make sure and be at the Women in Technology luncheon. I even volunteered to be a room monitor for a few sessions on Thursday to help out in other ways (although the last time I monitored a session the demo crashed, so I hope that’s not an omen). I’m sure I’ll do even more than this as impromptu get togethers will take place while I’m there, so I’ll meet someone for breakfast Thursday morning or make plans in the hall for dinner. And of course, I’ll be attending a bunch of sessions in addition to presenting. That’s a lot for a couple of days, but that’s how I’m going to get the most out of SQL Rally. I’m not planning on getting a lot of sleep or watching TV in my hotel room.
Welcome to Columnstores
Columnstore indexing is one of the new features provided by SQL Server 2012 that make it easier to break through the barriers of BI adoption for you. It’s a simple but powerful data structure that requires planning and special considerations. I hope to see you at my session where I’ll provide a thorough breakdown of Columnstore indexing and the best ways to use it in your own BI environment.
Have you put in your vote for which sessions you’d like to see at SQL Rally? If not then cast your vote here so you can get the most out of your time this May in Dallas. All it takes is to be a member of PASS and a few minutes.
I have a session on the ballot that’s called Using Columnstore Indexes in SQL Server 2012 and below is the session abstract for you to review. You might not be sure whether to vote for my session or you don’t know whether you need to attend session on columnstore indexes, so I’ll give you one really good reason.
The Reason for Learning about Columnstores
Columnstore Indexes are really important because in SQL Server 2012 they will have to be seriously considered by DBAs and BI Architects as a replacement for cubes (or as an alternative) and as the primary indexing scheme for star schemas, report subsytems, data warehouses and any other reporting and analysis scenario. Making the right decision will require you to have in-depth knowledge of how these indexes work. That’s what you’ll get if you attend my session.
Session Abstract: Using Columnstore Indexes in SQL Server 2012
Columnstore Indexes in SQL Server 2012 will allow you to significantly improve the processing time of common data warehousing queries without creating cubes, aggregated tables, or other techniques normally used to improve performance. This session will show how to implement this new type of index in SQL Server and demonstrate their advantages compared to traditional solutions. Carlos will also discuss the scenarios for which columnstore indexes should be implemented to provide powerful but flexible BI solutions.
Go to this blog post I wrote several weeks ago for more info on columnstore indexes.