San Francisco, California
London, United Kingdom
It has become a PASS Summit tradition to do a 3-mile run (#SQLRun !) on the Wednesday of the conference. But we're database pros, and we go above and beyond.
Enter the SQL Long Run (#SQLLongRun, naturally). 3 miles is a warmup. We'll do a minimum of 11 miles. Why? Because we can. And also because we want to offset the impact of sitting around a convention center all week. And also because it'll be fun.
This event is being generously sponsored by SQL Sentry, makers of high-end SQL Server monitoring tools.
Yanni Robel, Seattle-area SQL Server expert and marathoner, has helped to put together two routes: An 11-mile base route, and a 14-mile longer route.
11-mile map: http://www.mapmyrun.com/routes/view/562024422
14-mile map: http://www.mapmyrun.com/routes/view/562024300
Which route you run is up to you.
I don't want anyone to feel excluded from this event. I believe that unless you're in horrendous shape, you can start training now and you'll be able to complete the 11-mile route. That said, I also don't want more experienced runners to opt out due to fear of boredom, and a few of them so far have asked whether they can run at a faster pace.
I believe that as this is a community event, we should strive to keep the community feel as much as possible. This is not a race. Having a slower group come in when the faster group is already finished and gone? That doesn't feel very community to me.
The current working idea is that everyone will start together, and naturally break out into a few pace groups. The faster group(s) will start and run the same route as the slower pace group(s), but optionally some or all of these people can decide to take an additional 3-mile loop somewhere in the middle (that second route Yanni is working on). If everything goes as planned the faster group(s) should "catch up" with the slower group(s) toward the end, and I hope that all or most people will finish at about the same time, with the same sense of achievement and satisfaction.
This is a long enough run that hydration becomes a concern. SQL Sentry will provide a hydration station, somewhere around the middle of the route. But that's almost certainly not enough. If you're going to run with us you should bring a personal hydration system. There are a number of systems on the market, ranging from an inexpensive bottle that you can strap to your hand, to a belt system with a few bottles, to a backpack that can hold a large amount of water. In any case, you should consider the hydration station to be a refill station, NOT your only source of fluid.
We are a community of teachers and sharers and I'm quite certain that if you need training help you'll get as much as you can handle. Tweet to the hash tag -- #SQLLongRun -- and if you don't get a reply I'll make sure to pester some of our more experienced runners on your behalf.
Our sponsor, SQL Sentry (did I mention how generous they are?) is going to print us some #SQLLongRun running shirts. These will be collectable and no doubt will fetch a very high price at auction. But you need to show up and run to get one!
Ask on Twitter and I'll keep this space updated as we get closer to the event.
When & Where
SQL Server MVP and Running Addict