Thanks to all who attended SharePoint Saturday in Kansas City! I presented several sessions in the developer track, including WCF and AJAX on SharePoint 2007.

I've uploaded my slides (WCF in SharePoint 2007, and developing dynamic AJAX applications on the SharePoint platform) to the following SkyDrive folder:

href="http://cid-d3543c5837291e93.skydrive.live.com/browse.aspx/Public/Kansas SPSaturday">http://cid-d3543c5837291e93.skydrive.live.com/browse.aspx/Public/Kansas%20SPSaturday

I'll post additional code samples soon-- most code is from my new AJAX book (google: "service oriented ajax"). 

The open source

AJAX library for SharePoint that I used, the "SharePoint AJAX Toolkit", is located at http://www.codeplex.com/sharepointajax. Get the LATEST SOURCE CODE, skip the release, as I'm usually pretty lazy at building official releases. You can also subscribe to the project feed here. A quick recap: this library safely wraps the Microsoft AJAX Library and adds a JavaScript control that takes Xml and Xslt URL parameters, and wraps it in an AJAX Xml Web Part.

As a demo, we built a Site Chat component using the XmlControl JavaScript class deployed in a Web Part, talking to a WCF endpoint. The full code for this part is in the code downloads for my AJAX book (google: "service oriented ajax"). Here's a screenshot:

In the next few days I'll post some more details, and the whitepaper for WCF support in SharePoint 2007.

The blog entry I posted a month or so ago about XLCubed where I had a pop at Microsoft for their client tool strategy certainly seemed to strike a chord with a lot of people (see the comments, and also Marco's blog entry here). It also made me think that it would be worth spending a few blog entries looking at some of the new third party client tools that are out there... I've already lined up a few reviews, but if you've got an interesting, innovative client tool for Analysis Services that I could blog about, why not drop me an email?

So anyway, the big news last week was of course Google's announcement of Chrome. And as several of the more informed bloggers (eg Nick Carr, Tim McCoy) the point of Chrome is to be not so much a browser as a platform for online applications, leading to a world where there is no obvious distinction between online and offline applications. And naturally when I think about applications I think about BI applications, and of course thinking about online BI applications and Google I thought of Panorama - who incidentally this week released the latest version of their gadget for Google Docs:
http://www.panorama.com/newsletter/2008/sept/new-gadget.html

Now, I'll be honest and say that I've had a play with it and it is very slow and there are a few bugs still around. But it's a beta, and I'm told that it's running on a test server and performance will be better once it is released, and anyway it's only part of a wider client tool story (outlined and analysed nicely by Nigel Pendse here

) which starts in the full Novaview client and involves the ability to publish views into Google Docs for a wider audience and for collaboration. I guess it's a step towards the long-promised future where the desktop PC will have withered away into nothing more than a machine to run a browser on, and all our BI apps and all our data will be accessible over the web.

This all makes me wonder what BI will be like in the future... What will it be like? Time for some wild, half-formed speculation:

• Starting at the back, the first objection raised to a purely 'BI in the cloud' architecture is that you've got to upload your data to it somehow. Do you fancy trying to push what you load into your data warehouse every day up to some kind of web service? I thought not. So I think 'BI in the cloud' architecture is only going to be feasible when most of your source data lives in the cloud already, possibly in something something like SQL Server Data Services or Amazon Simple DB or Google BigTable; or possibly in a hosted app like Salesforce.com. This requirement puts us a long way into the future already, although for smaller data volumes and one-off analyses perhaps it's not so much an issue.
• You also need your organisation to accept the idea of storing its most valuable data in someone else's data centre. Now I'm not saying this as a kind of "why don't those luddites hurry up and accept this cool new thing"-type comment, because there are some very valid objections to be made to the idea of cloud computing at the moment, like: can I guarantee good service levels? Will the vendor I chose go bust, or get bought, or otherwise disappear in a year or two? What are the legal implications of moving data to the cloud and possibly across borders? It will be a while before there are good answers to these questions and even when there are, there's going to be a lot of inertia that needs to be overcome.
  The analogy most commonly used to describe the brave new world of cloud computing is with the utility industry: you should be able to treat IT like electricity or water and treat it like a service you can plug into whenever you want, and be able to assume it will be there when you need it (see, for example, "The Big Switch"
  
  ). As far as data goes, though, I think a better analogy is with the development of the banking industry. At the moment we treat data in the same way that a medieval lord treated his money: everyone has their own equivalent of a big strong wooden box in the castle where the gold is kept, in the form of their own data centre. Nowadays the advantages of keeping money in the bank are clear - why worry about thieves breaking in and stealing your gold in the night, why go to the effort of moving all those heavy bags of gold around yourself, when it's much safer and easier to manage and move money about when it's in the bank? We may never physically see the money we possess but we know where it is and we can get at it when we need it. And I think the same attitude will be taken of data in the long run, but it does need a leap of faith to get there (how many people still keep money hidden in a jam jar in a kitchen cupboard?). 
• Once your data's in the cloud, you're going to want to load it into a hosted data warehouse of some kind, and I don't think that's too much to imagine given the cloud databases already mentioned. But how to load and transform it? Not so much of an issue if you're doing ELT, but for ETL you'd need a whole bunch of new hosted ETL services to do this. I see Informatica has one in Informatica On Demand; I'm sure there are others.
• You're also going to want some kind of analytical engine on top - Analysis Services in the cloud anyone? Maybe not quite yet, but companies like Vertica (http://www.vertica.com/company/news_and_events/20080513) and Kognitio (http://www.kognitio.com/services/businessintelligence/daas.php) are pushing into this area already; the architecture this new generation of shared-nothing MPP databases surely lends itself well to the cloud model: if you need better performance you just reach for your credit card and buy a new node.
• You then want to expose it to applications which can consume this data, and in my opinion the best way of doing this is of course through an OLAP/XMLA layer. In the case of Vertica you can already put Mondrian on top of it (http://www.vertica.com/company/news_and_events/20080212) so you can already have this if you want it, but I suspect that you'd have to invest as much time and money to make the OLAP layer scale as you had invested to make the underlying database scale, otherwise it would end up being a bottleneck. What's the use of having a high-performance database if your OLAP tool can't turn an MDX query, especially one with lots of calculations, into an efficient set of SQL queries and perform the calculations as fast as possible? Think of all the work that has gone into AS2008 to improve the performance of MDX calculations - the performance improvements compared to AS2005 are massive in some cases, and the AS team haven't even tackled the problem of parallelism in the formula engine at all yet (and I'm not sure if they even want to, or if it's a good idea). Again there's been a lot of buzz recently about the implementation of MapReduce by Aster and Greenplum to perform parallel processing within the data warehouse, which although it aims to solve a slightly different set of problems, it nonetheless shows that problem is being thought about.
• Then it's onto the client itself. Let's not talk about great improvements in usability and functionality, because I'm sure badly designed software will be as common in the future as it is today. It's going to be delivered over the web via whatever the browser has evolved into, and will certainly use whatever modish technologies are the equivalent of today's Silverlight, Flash, AJAX etc.  But will it be a stand-alone, specialised BI client tool, or will there just be BI features in online spreadsheets(or whatever online spreadsheets have evolved into)? Undoubtedly there will be good examples of both but I think the latter will prevail. It's true even today that users prefer their data in Excel, the place they eventually want to work with their data; the trend would move even faster if MS pulled their finger out and put some serious BI features in Excel...
  In the short-term this raises an interesting question though: do you release a product which, like Panorama's gadget, works with the current generation of clunky online apps in the hope that you can grow with them? Or do you, like Good Data and Birst (which I just heard about yesterday, and will be taking a closer look at soon) create your own complete, self-contained BI environment which gives a much better experience now but which could end up being an online dead-end? It all depends on how quickly the likes of Google and Microsoft (which is supposedly going to be
  
  revealing more about its online services platform soon) can deliver usable online apps; they have the deep pockets to be able to finance these apps for a few releases while they grow into something people want to use, but can smaller companies like Panorama survive long enough to reap the rewards? Panorama has a traditional BI business that could certainly keep it afloat, although one wonders whether they are angled to be acquired by Google.

So there we go, just a few thoughts I had. Anyone got any comments? I like a good discussion!

UPDATE: some more details on Panorama's future direction can be found here:
http://www.panorama.com/blog/?p=118

In the months to come, Panorama plans to release more capabilities for its new Software as a Service (SaaS) offering and its solution for Google Apps.  Some of the new functionality will include RSS support, advanced exception and alerting, new visualization capabilities, support for data from Salesforce, SAP and Microsoft Dynamics, as well as new social capabilities.

There's going to be another one of the UK SQL Server Community's BI Evening events happening at Microsoft UK's offices at TVP in Reading on the evening of July 17th. It's been far too long since the last one, I know - we've all been a bit distracted by SQLBits (

and there's going to be another one of those on September 13th - do you or our company want to sponsor it?).

You can sign up here:
http://www.sqlserverfaq.com/

Here's what we've got lined up:

"PEL vs MDX - what are the differences between the two languages?"
Jeremy Kashel, Adatis

Jeremy Kashel from Adatis  presents an introduction to the PerformancePoint Expression Language (PEL). The content will be geared towards MS BI developers, and will highlight the differences between PEL and MDX, with the aim that those with MDX experience will be able to make a fast start with PEL

"Using Excel Services with Analysis Services and MOSS"
Jeremy Kirkup, TAH

If you are just starting to explore delivering BI solutions with Excel Services and Sharepoint then there are some issues that it is wise to be aware of in advance. This session will describe some real world lessons gained while creating BI solutions which expose Analysis Services data through the Excel Web Access web part.
The Excel 2007 client has first class support for the some of the advanced features of Analysis services such as drill-through.  However, when exposing pivot tables to a browser through the Excel Web Access web part this feature is not available. The session will discuss a couple of approaches to implementing drill-through functionality for EWA based pivot tables using the MOSS SmartPart, AJAX and the Excel Web Services.