We arrived yesterday at Seattle after traveling for 19 hours strait. After checking into The Paramount Hotel we went to Fox Sports Grill. They had everything a guy is looking for. Football on TV, Streaks on white toasted bread and a beer :) Great evening.
Normally I feel very uncomfortable meeting new people so I try to avoid it. But reading up on all the great tips for SQL PASS Summit and what I see over and over again is the words networking and meeting new people. So I decided that to get the most out of this I will try to meet some new people each day.
And to insure that I at least meet some new people I will put it into writing that I will at least try to meet the following people:
Brent Ozar
This guy really kicked my interest into diving deeper into the SQL Server. I attended one of his online web casts on how to take over a SQL Server. I was so excited after hearing his enthusiasm about the SQL Server. I thing they where three guys and the really had a lot of fun. I was sold and he might be the reason why (besides my company how send me) I'm here today. He kick started things for us. So this guy I want to meet.
Jes Borland
I joined twitter to figure out more about this Summit and to try to learn some people beforehand. And this girl are hard to miss on twitter :) She is a sheer energy bomb. She has already, even though she is quite young, done so much. Actually I thing she is running her first half marathon today. I can relate to this. I remember every inch of my first half marathon a couple of year ago. This girl I just have to meet.
Pinal Dave
I have used a script for many years to find unused indexes. This was blog post has been my first bookmark in the browsers bookmark bar. So this is used quite a lot. I find out that this post well the entire blog is written by Dave and he is coming to the Summit as well. So this would be kind of fun to get a chance to say thanks and let him know what a important part of my DBA life this one post has.
Jason Strate
Well have you seen his videos pre-con :) I'm still laughing just thinking about it :D Well him and his wife are very dedicated to the SQL Server community. I like to meet people like that which burns with such passion for there "believes" :) And then he is from Minnesota. I lived there for a year (go Vikings :) - I even brought my Vikings Bret Farve jersey). This time in MN I have looked back up for the last 26 years with a lot of joy So him and his wife I like to meet.
And many more...
There are a lots of out people I like to meet but lets start here. And if you see me at the summit and are not afraid of new people like me - please come and say Hi to me. You can find me on twitter as well.
Now its time for a hot bath and some breakfast before we go out to see Seattle. I need to get a convert for my electronic equitment and then I would like to see if its possible to buy a small mobil data packet just for this week. The iPhone are best with data but it cost the tip of an fighter jet (so my boss says) on our Danish mobil provider when we are over here.
Sunday, October 9, 2011
Friday, September 30, 2011
SQL PASS Summit plans
I think I have my execution plan for the summit ready. Me and my co-worker will leave Denmark on Saturday the 8th of October around noon - yes that's only a week from now :) Yeahhhhhhh
We have to fly to Amsterdam and from there to Seattle where we will be a couple of hours later - not considering the time difference :) So it will only be around 5pm when we arrive at the SEA airport.
We are staying at The Paramount, in working distance from the summit - even after a few drinks.
I was hoping to catch a Seahaws game that weekend but unfortunately there play away. I'm a big fan of american football (called that here since we call soccer for football :)) so it would have been nice to see a live game. Even though I'm a Vikings fan - that would have been great. Anybody know if there is a college football game that weekend near by? Wachington Huskies an't playing the weekend at the arrival.
Well I guess we will just take care of the jet lag on Saturday and maybe get a steak :) love steaks. But on Sunday it will be time to see Seattle. We both know another great Dane which comes to the summit and I would love to try to do some stuff with him on Sunday. Maybe a look at one off my troubled SQL Servers over drinks :) See that would be a nice day!
As this is my first trip to the summit I don't really know what I'll (we) doing in the evenings. But I like to mingle so I will figure out something to do. Hopefully I find someone which wants to talk about SQL stuff over a couple of whiskeys - my two top choices. You too? Then we have a play date lined up.
From Monday it's all about the summit. My current plan looks like this:
This is my priority right at this moment anyway.
And on Saturday we go back :( at lunch time. I guess the plan on moving Europe during that week because the flight back to Denmark takes almost 24 hours - we are not home before Sunday afternoon :) Well I might have to learn something about time zones.
We have to fly to Amsterdam and from there to Seattle where we will be a couple of hours later - not considering the time difference :) So it will only be around 5pm when we arrive at the SEA airport.
We are staying at The Paramount, in working distance from the summit - even after a few drinks.
I was hoping to catch a Seahaws game that weekend but unfortunately there play away. I'm a big fan of american football (called that here since we call soccer for football :)) so it would have been nice to see a live game. Even though I'm a Vikings fan - that would have been great. Anybody know if there is a college football game that weekend near by? Wachington Huskies an't playing the weekend at the arrival.
Well I guess we will just take care of the jet lag on Saturday and maybe get a steak :) love steaks. But on Sunday it will be time to see Seattle. We both know another great Dane which comes to the summit and I would love to try to do some stuff with him on Sunday. Maybe a look at one off my troubled SQL Servers over drinks :) See that would be a nice day!
As this is my first trip to the summit I don't really know what I'll (we) doing in the evenings. But I like to mingle so I will figure out something to do. Hopefully I find someone which wants to talk about SQL stuff over a couple of whiskeys - my two top choices. You too? Then we have a play date lined up.
From Monday it's all about the summit. My current plan looks like this:
This is my priority right at this moment anyway.
And on Saturday we go back :( at lunch time. I guess the plan on moving Europe during that week because the flight back to Denmark takes almost 24 hours - we are not home before Sunday afternoon :) Well I might have to learn something about time zones.
Thursday, September 29, 2011
Let the little ones join up first
The order of tables in a join - third blog in my series "From newbie to DBA"
In my last blog I promised to look at the simple way to use the execution plan. That will have to wait as I just remember another important tip I found some time ago to easily bust performance when handling large amount of data. And it leads up to one of the things I found to look for en the execution plan.
It's kinda up the ball park with my last post. Its all about giving the SQL Server the best information to work with.
When you make joins between a large table and a smaller one the order of the tables does matter. If I for instance make this query:
select * from BigTable a
inner join SmallTable b on a.Key1 = b.Key1 and a.Key2 = b.Key2
then everything is runned based on BigTable. Back to the selectivity I talked about ind the last post. You start out with a large amount of data and then you select out based on the small amount. Then yYou have a large amount of data to match up.
But if you instead use the SmallTable as base:
select * from SmallTable a
inner join BigTable b on a.Key1 = b.Key1 and a.Key2 = b.Key2
In my last blog I promised to look at the simple way to use the execution plan. That will have to wait as I just remember another important tip I found some time ago to easily bust performance when handling large amount of data. And it leads up to one of the things I found to look for en the execution plan.
It's kinda up the ball park with my last post. Its all about giving the SQL Server the best information to work with.
When you make joins between a large table and a smaller one the order of the tables does matter. If I for instance make this query:
select * from BigTable a
inner join SmallTable b on a.Key1 = b.Key1 and a.Key2 = b.Key2
then everything is runned based on BigTable. Back to the selectivity I talked about ind the last post. You start out with a large amount of data and then you select out based on the small amount. Then yYou have a large amount of data to match up.
But if you instead use the SmallTable as base:
select * from SmallTable a
inner join BigTable b on a.Key1 = b.Key1 and a.Key2 = b.Key2
In this case you only have a small amount of data to match up. And you have already reduced the amount of data SQL Server has to go through in order to give you the result.
Its all about high selectivity. And you can see if your query uses small over large right away in the execution plan. More on that later. But you should all the time have in mind that the fastest solution is high selectivity
Labels:
dba,
join,
large table
Subscribe to:
Posts (Atom)