Three quick news updates

May 27, 2011

A few quick items for this Friday, then I’m off to Cedar Point for some much-needed coaster thrills:

1) HostedPowerPivot Interest – Wow!

We’re blown away by the response to HostedPowerPivot.com.  I’ve spent multiple hours on the phone today with longtime blog readers – an added benefit of this is getting to know some of you better.  Very cool, seeing all the different usage cases people have in mind.

2) Webinar with Rackspace June 8th

I’m going to be doing a PowerPivot webinar with Jeff DeVerter, SharePoint guru at Rackspace, on June 8th.  It’s going to be more of an intro to PowerPivot, so longtime readers here may find it elementary.  But there will be some fun demos, and Jeff is a really dynamic personality, so I am looking forward to it.

Click here to view the agenda, and to reserve a spot

3) Part two of “portable formulas” is live on the Excel blog

I’m 100% serious that formula portability is one of the top 3 benefits of PowerPivot over normal Excel, it’s just taken me awhile to figure out how to explain it.

Click here for part two

…and here if you missed part one


HostedPowerPivot.com from Pivotstream & Rackspace

May 25, 2011

Click for HostedPowerPivot.com
No, we're not villains.  But the quote was too perfect to pass up!

“At last we will reveal ourselves to the Jedi Bee-I.  At last we will have shared intelligence.”

A secret long kept, finally revealed

It’s a recurring theme – I see it in my training/consulting practice, in my inbox, in the survey results, and at events: 

“We LOVE PowerPivot.  It’s a perfect fit for our analysis and reporting needs.  But our company has not yet adopted SharePoint, and we don’t have the in-house expertise to stand up and support PowerPivot for SharePoint.    We just want the simple beauty of PowerPivot, we want it now, and it’s frustrating that we can’t have the full system yet.”

I hear you.  That is precisely where we found ourselves when I joined Pivotstream.  The lack of a “turnkey” solution to that problem meant we had to go build it ourselves.  And our core business has been running on our internet-based PowerPivot infrastructure since last summer.

But now, one year and two hosting providers later, we are finally able to share what we’ve built with the community.

A Long, Long Time Ago, In a Conference Room Far, Far Away…

OK, it was February, in San Antonio.  John Casey and I were at Rackspace headquarters for two full days to pitch an idea:  that an all-in-one, customized-to-your-needs, zero-hassle PowerPivot for SharePoint infrastructure would be a very valuable thing to the world at large.

We’d chosen Rackspace based partly on their reputation for support, but primarily because they had the most SharePoint expertise in the hosting business.  SharePoint, after all, is probably the most complicated part of running a PowerPivot server farm.  We were already moving our own server farm over to Rackspace at that point, but now we were pitching them on a partnership.

It’s a dicey proposition, walking into someone else’s offices knowing that you have to start from scratch.  We planned to cover the dynamics of the BI market, past and present, Excel’s place in it, Microsoft’s first-ever total alignment on a strategy, and why imagePowerPivot was going to change the world.  That’s a tall order for anyone to digest or believe in a short two days, no matter how fervently I believed in the message myself.

I underestimated them.  They understood perfectly.  We ended up meeting with 10-12 members of their leadership team over those two days, transitioning from “here’s a cool idea” to “here’s how we can execute.”

Keeping this a secret has been the longest three months of my life.  I am stoked that the waiting is over.

Want the short version?

Being that this is a blog – my blog, specifically – and that I love telling stories, my aim here is to describe how we got here – motivations, steps along the way, etc.

But if you just want to get to the “meat” of this, and/or request more information, go ahead and visit HostedPowerPivot.com:

Click for HostedPowerPivot.com

Ok, back to the story.

Thanking Rackspace

I’m pretty sure we could not have done this HostedPowerPivot thing with anyone else, although I did not fully understand that going in.

We’ve been running our core PowerPivot platform in a Rackspace data center for four months, and the level of support we get from them is night and day different from what we had in our last data center.  They advertise “fanatical support,” and I’m a believer now.

As fantastic as that is, though, the word “support” doesn’t capture what continually impresses me.  I keep coming back to the human element – the real people on the other end who are acting like human beings and not cogs in a machine.  I’m not accustomed to big established companies, especially infrastructure companies, maintaining a nimble, entrepreneurial vibe, but that’s what I’ve found here.

For instance, does this sound like “support” to you?

Me:  “Hey Rackspace, we’ve found some unexpected PowerPivot performance results on this hardware set.  We’re now running some tests on every hardware platform we’ve got.”
Rackspace:  “Are there some other hardware options we can try out for you?  We’ve got access to a bunch of stuff here you know.”
Me:  “YES.  You’d need to install PowerPivot and run a bunch of tests on each machine, do you have time for that?”
Rackspace:  “No problem.  Send us the instructions and we’ll try it on 10 different machine types.”

Rackspace:  “OK, here’s a detailed spreadsheet of our results.  Three test runs for each unique config, reported separately and then averaged.”
Me:  “Did you say spreadsheet?  I think I’m in love.  We’ll correlate that with our other results.”

Me:  “OK based on all results, the best query performance would be achieved on a non-standard config, one with the following properties…  is that machine something that can be built out in your datacenters as THE standard PowerPivot server?”
Rackspace:  “Hmmm…  we’ll look into it and get back to you.”

Rackspace:  “Yes, we have approval to build that out.  Should we order one up for testing purposes?  We’ll have to have some new equipment delivered from the hardware vendor, might take a few days.”
Me:  “Yes please.”

Rackspace:  “Test machine racked and running.  And uh, I think you will be pleased.  It’s blowing the socks off of everything else we tested!”
Me:  “I love it when a plan comes together.  Gentlemen, we have ourselves a PowerPivot server.”

Thanks guys.  Too many of you to name specifically, but you know who you are Smile

Step 1:  Register Domain.  Step 2:  Submerge in PowerPivot for a year

True story:  Jeff Elderton, our CEO at Pivotstream, registered the domain HostedPowerPivot.com before we even decided I was going to sign on.  It’s been in our plans from the beginning.  But before we could credibly do such a thing, we first had to apply the technology ourselves, for our own core business.  We dug into that while PowerPivot was still in beta, as our sole focus.

Along the way we had to solve all of the common problems everyone will hit.  We’ve written software to plug the gaps and provide a professional aesthetic.  We know how to “capacity plan” specifically for PowerPivot.  We’ve even figured out that certain hardware configurations can dramatically outperform the most commonly-used server configs.  We learned a lot more than we expected to.

All of that was expensive and time-consuming of course.  But it was absolutely worth it.  The things we deliver to our customers simply were not possible before PowerPivot.

Today, I’m pretty sure no one in the world runs a PowerPivot infrastructure of the depth and breadth of what we run at Pivotstream.  Our entire core business (subscription analytics for dozens of clients) runs on our PowerPivot infrastructure.  There’s no substitute for just doing something – I learned much more about PowerPivot from the outside, as an adopter, than I did as an insider, working on the team at MS.  That was surprising, although it makes sense in hindsight.

I’m really happy to see it all come full circle.  At his core, Amir Netz describes himself as an inventor.  I like that, I think it fits him quite well.  I’m similar in some ways, but it’s not like I will ever come up with something like the VertiPaq engine, so “Inventor” would be an overly generous description of me.  I like to think of myself as a creator.  I love creating useful things.  I love filling voids.  And this one has had me jazzed for a very long time.

1997:  Alabama 20, Vanderbilt 0

There’s one more story I’d like to tell, and it’s a bit of a cliffhanger because it deserves its own post.  Like so many other things around this blog, it all comes back to football:  there’s a connection between us hooking up with Rackspace, and the 1997 Alabama routine thrashing of Vanderbilt.

Just one of those fun little wrinkles in life.
 

Click here for THRILLING highlights. I wonder who posted these? Hmmm…

A Lesson in A-G-I-L-I-T-Y

May 11, 2011

image

A case study I just have to share

Over the past year, “Agility” has become quite a theme on this blog.  It’s fair to say that I just keep hammering it, over and over.  But I recently had my eyes opened as to what “extreme” PowerPivot agility can look like.

Let’s put it in football terms:  it’s like I’ve been going around telling everyone how they should be less like the 400+ pound Aaron Gibson and more like the nimble, versatile Marshall Faulk.

And then someone comes along like Barry Sanders:  agile in ways that you’d never think to recommend, but once you see it, you recognize it immediately.  And then you watch it over and over in awed slow-motion (seriously, click Barry’s name above for a video). 

That’s what this is like.

Dynamic Data Warehousing!

You don’t truly know what you need to know, until you are delivered what you THOUGHT you needed to know (I sound like Rumsfeld).  That was the theme of this blog post from last year.  That blog post concluded with my clients at the time realizing that the data they truly needed…  wasn’t even being collected.

I think it’s basic human nature to assume that yesterday’s gaps in your understanding are just that (yesterday’s), and that you won’t suffer from that in the future.  Marcellus Wallace recognized this tendency as pride, and rightly took a dim view of its helpfulness. (Video definitely NSFW!)

I’ve sung the praises of those folks (my clients) before, and I’m going to do it again:  Pride didn’t get in the way of their thinking on this issue.  Instead of telling themselves that they’d be better at anticipating their needs in the future, they decided to bake uncertainty into the CORE of their BI planning. 

They built a system that enables the following:  If they decide they are missing a set of data points, they can start collecting them, warehousing them, and analyzing them, end to end, in as little as two to four days’ time (that’s my estimate).

Here’s a diagram to illustrate:

image

Click for larger version

More Detail

Here’s some detail that was hard to fit into the diagram.  Basically these folks have millions of devices out “in the wild,” and those devices are instrumented to collect data about usage patterns.  When I first visited them in the early Fall, those devices were hardwired to collect only fixed data points, and we discovered that they needed to collect new data.

When I had the opportunity to drop back in on them recently, however, they revealed this new system.  Now, the only thing hardwired is flexibility.  The devices all call home once a day and see if there are new instructions awaiting them – brand new script written by their development team.  To make things painless and error-free for the development team, they also have built an internal portal that the developer visits to register the new message type that they are adding to the devices’ instrumentation scripts.  That portal takes care of configuring the data warehouse – new tables, retention policies, aggregation rules, as well as configuring the incoming message ports and mapping them into the right import processes.  Boom.

imageThey are even experimenting with ways to allow automatic generation and/or modification of PowerPivot models based on selections made in the portal.

It’s worth taking a step back and marveling at.  On Monday they can realize they have a blind spot in their radar.  On Tuesday and Wednesday they develop and test new instrumentation code.  On Thursday they roll it out to the devices.  And on Friday, they are literally collecting and analyzing MILLIONS of data points per day that they lacked at the beginning of the week.

It’s not like those new data points are on an island, either.  Via DeviceID, they are linked to multiple lookup/dimension tables and therefore can be integrated into the analysis performed on other fact/data point tables as well.  They can literally write measures that compare the newly-collected data against data they were already collecting – ratios, deltas, etc.  They can put the new metrics side by side with old metrics in a single pivot.  And, in theory, they could use the new data points to generate new lookup/dimension tables by tagging devices that exhibit high or low amounts of the newly-instrumented behaviors (although we did not discuss that on site – it just struck me as a possibility).

And late last year this organization had made zero investment, ZERO, in business intelligence.

Can this work for everyone?

Of course not.  Not everyone has the luxury of reprogramming their production systems at high frequency like this.  Not everyone can afford the risk or performance hit of having their production systems writing back directly to their data warehousing systems either – standard practice is to have your warehousing efforts “spying” on your transactional systems and taking occasional snapshots.  It’s a pull, not a push, which is why the “E” in “ETL” is Extract.

But this is definitely food for thought, for everyone.  “Why not?” is one of my favorite questions, because even if you can’t ultimately do something, examining the “why not” in detail is often very enlightening.

I know one of the standard objections is going to be, essentially, “Data Gone Wild:  No discipline.  Mile-long lists of tables and fields.”  Bah, I say!  Good problems to have!  Storage is cheap, flying blind is expensive.  And when you reach the point of being blinded by too much information, well, that’s an opportunity for a new set of tools and disciplines.

More to come

Last week was my first ever “doubleheader” – two consulting/training clients in a single week.  That can be hard on a blogger, heh heh.  But I look to be home for the next week or two, so you should expect to see a renewed flow of content here.  Got several things rattling around in my head.


Portable Formulas: An Underestimated Benefit

May 5, 2011

 
image

Neo: Are you saying that I can copy/paste formulas?
Morpheus: No Neo, I’m saying that you won’t have to.

 

 

Hi folks.  Sorry about the lack of posts lately.  I’ve been on the road.  A lot.  This week I’m doing a doubleheader – consulting/training in New Mexico and then California, so I’m writing this on a plane between Denver and San Diego.  (I recently joked that I’m the PowerPivot version of Tyler Durden – never sleeping, crisscrossing the country setting up franchises of Pivot Club).  PowerPivot adoption is rapidly picking up and that has the ironic side effect of taking me away from the blog.

But the other reason I’ve been so quiet is that I submitted a two-part post to Microsoft’s official Excel blog rather than posting it here.  Some posts just “speak” to the Excel audience better than others, and this is one that I really want as many Excel folks to see as possible.  The majority of Excel pros have yet to discover PowerPivot, and I love being the bearer of good news.

The post is actually about an inherent weakness in all traditional spreadsheets.  One that I believe eats more than half of the average Excel pro’s time, if not more.  A weakness that PowerPivot obliterates… with a concept that I am calling Portable Formulas.

Part one of two is live today: Click here to view it on the Excel blog.