Microsoft Master Data Mangement Release announced

Microsoft’s Master Data Management tool, previously codenamed ‘Bulldog’ and slated to be included in the Office 14 release is now set to be included with Kilimanjaro – which seems to now be officially called SQL Server 2008 R2.

More details can be found at the SQL 2008 Official site. The rumour mill seems to imply that SQL 2008 R2 will drop at roughy the same time as Windows 7.

Just in case you have no idea what Master Data Management entails, it covers managing and centralising metadata within an organisation that may span many systems. The most common example is central management of customer records. For more insight and a more detailed explanation, I suggest you read this white paper on the subject by Roger Wolter and Kirk Haselden.

Kilimanjaro, Projects Gemini and Madison Webcast

For those who haven’t seen much of Project Gemini but have heard the buzz, this TechNet Webcast: An Early look at SQL Server ‘Kilimanjaro’ and project ‘Madison’ – will give you a good insight. It also has some features on reusable Reporting Services components which look very impressive and info on Project Madison, which provides scalability features. Registration as usual is a pain, and forget trying to use the site using any browser other than IE – I wish Microsoft would make their content easier to access.

Anyway, onto the webcast – about the 1st quarter of the webcast is the usual generic roadmap blurb, but then the presenter gets into the real meat of Gemini – an Excel based ‘in memory’ analysis tool that allows joining between entities without having to know about such things, superfast analytics – pivoting, calculation, charts etc. and then being able to publish to Sharepoint. From an OLAP analysis point of view, the Pivot Tables also has slicers (effctively table wide filters) displayed in the spreadsheet as well, and it would be good if that made it into Pivot Tables generally in the next release of Office. It looks like an incredible tool and very easy to use – and may be a powerful step towards the realisation of the ‘BI for the masses’ vision. The presenter did let slip one weakness though – much has been made of the 100 million rows of data demo – but that data still has to be loaded into memory first and will still take significant time. I also suspect that how successful Gemini will be is going to depend on how much it will rely on good data structures being in place in an organisation to support it. The Data Warehouse is going to remain the core part of  any succesful BI delivery.

The next component of interest was the reusable Reporting Services components – there is the concept of a library of components that can be built – e.g. standard charts, logos, gauges etc – and then dropped into any report, either by a developer or a user in Report Builder 2.0.  What really grabbed my attention is that these components are version aware – i.e. if the library version of the component is updated then if you reopen the report in design mode it will let you know and give you the option to update. Again this points to ‘BI for the masses’ as you can have developers create some great components which any user can then drop in to their home grown reports. Plus as any developer knows, there’s a lot of repetition and any options for code re-use are always appreciated.

Finally, Project Madison was covered – and seems more about scalability up to multi-terabyte warehouses. It was a bit infrastructure focused for me so most of it passed me by, but clearly Microsoft are stepping up to try and address the market perception that they can’t scale.

Anyway, this all will be dropped in late 2010 as Kilimanjaro – an interim release of SQL Server.

SSWUG Virtual Conference & New blog links

I have picked up from the SSIS Team blog the upcoming SQL Server World User Group (SSWUG) Virtual Conference from April 22-24. The Virtual Conference will all be scheduled in American time, so unless you happen to be active between 11pm and 7am .au time, you won’t be able to watch the presentations live. However the presentations are all viewable for up to 2 weeks after the events. Attendance costs 125 US$, or about 175 AU$. There are some compelling presentations from well known industry figures on both SQL Server, and of interest to the BI Monkey, SQL Server BI. Full details for each can be found here for BI and here for SQL Server.

I’ve also added links in the Relevant Blogs section for the SSIS Team Blog and for Jamie Thompson’s excellent SSIS Junkie, where I have found more solutions to SSIS problems that anywhere else on the net.

Installing SQL Server 2005, 2008 and PerformancePoint 2007 on Windows Server 2008

A bit of a mouthful of a title, but I have discovered in the process of trying to build some Virtual Machines to play on, that the above four pieces of software are not always friends.

A clean install of PerformancePoint Server 2007 (PPS) against SQL Server 2008 (SQL2K8) is not directly possible, even at PPS Service Pack 2 (SP2). There is an approach documented on TechNet which involves installing some SQL2K5 components (See scenario 3 of this article: http://technet.microsoft.com/en-us/library/cc514367.aspx) but I couldn’t get it to play ball. I would guess that PPS2007 won’t properly integrate with SQL2K8 for a while yet, so if you are installing PPS2007, do it against SQL2K5 SP2.

Next up, SQL2K5 won’t install cleanly on a vanilla install of Windows Server 2008 (Win2K8). You need to enable the Web Server Role, and then enable features as described in this KnowledgeBase article (http://support.microsoft.com/kb/938245/) – it’s not complicated. It also throws up a warning to patch SQL2K5 to SP2 when running the installer, but I would advise you did that on any install anyway.

Installations are never easy!

SQL Server 2005 SP3 Released 15 Dec 2008

I’ve just spotted SQL Server 2005 SP3 was released just before Xmas. It doesn’t appear to be a major pack (like SP2) so I would only advise installing SP3 on fresh installs. Upgrading will only be critical if the service pack addresses a specific issue on existing servers. Any 2005 server not on SP2 should be upgraded at least to SP2, as i’ve noted before.

Full details here: http://msdn.microsoft.com/en-us/library/dd353312(SQL.90).aspx

Upgrade to SQL2005 SP2, you fools!

Hitting one of these 3 messages in SSIS on SQL2005?

  • The task is configured to pre-compile the script, but binary code is not found
  • The script component is configured to pre-compile the script, but binary code is not found
  • The task cannot execute in 64-bit environment because the script is not pre-compiled

Hotfixes are available here for Build 1399 and here for Build 1500

All the above can be fixed by applying SP2. And really, if you haven’t put SP2 on your SQL2005 you had better have a good reason for it, as there’s lots of other little things which will catch you out on your BI projects if you don’t. It was released in March 2007 so it’s not exactly a new patch either.

SQL 2008 New features

Time to take a break from BI based ramblings, and more importantly for my sanity, get the hell away from Cognos Data Mangler for a bit.

Recently I attended a SQL2008 skills update session to find out what’s new in SQL Server 2008. The answer is – from a manageability point of view – quite a lot. From a BI point of view, there’s two real stand out features.

First is the addition of the MERGE statement. This will be old hat to Oracle* users, but it allows you to do all your insert / updates in a single SQL statement as opposed to on a row by row basis. This delivers major performance advantages and will speed any ETL that delivers both new and changed rows to a table (in Oracle I managed to get a 20-fold improvement over row by row update / inserts). The only downside is this hasn’t been catered for in SSIS, so there’s scope out there for a custom component to take advantage of this.

Second is Change Data Capture (CDC). This captures in a mirror table – with metadata – any rows that are added or changed in a table on which CDC is enabled. Probably less relevant these days as most well designed databases will have update timestamps or versions, but a useful way of tracking changes in data – which ETL processes can then pick up on.

Otherwise there’s not much in SSIS, a new Office 2007 style interface for Reports, and things in SSAS which I don’t have a full handle on yet, but nothing groundbreaking. They have plugged some performance holes, but 2008 looks to be the administartion release, as 2005 was the BI release of the platform. Microsoft want to go head to head with Oracle, and assuming they can shake the perception that SQL Server isn’t scalable (which is is) then Oracle should start worrying. Because it’s usable and doesn’t require an expensive DBA and huge costs per feature.

As an aside, for geekery, the new spatial data type is incredibly cool…

« Previous Page