Saturday, February 26, 2011

Sql-Rd addon for Reporting Services

For those looking for Report Bursting and other complex scheduling, exporting, and printing requirements, this tool fills in the blanks with Reporting Services.

SQL-RD is a dynamic, flexible, function-rich and intuitive automation tool for scheduling, exporting, distributing and delivering your Microsoft® SQL Server Reporting Services (SSRS) Reports.



SQL-RD contains powerful system, event and business process automation functions which will make an instant impact on the efficiency of your business.

A couple of the cool features I saw were bulk printing to multiple printers, SMS text messaging, Zipped/PGP'd reports, deferred delivery, even an export to DBase option...

Thursday, February 24, 2011

Two new tools for diagnosing performance bottlenecks with SQL

TraceTune is designed to read SQL Server traces and tell you which SQL statements or or stored procedures are consuming the most resources. TraceTune is the online version of ClearTrace and is maintained by scaleSQL Consulting.


http://www.tracetune.com/





Project Lucy analyzes performance data that you upload. It gives you deep analysis and leverages the collective intelligence of other Project Lucy users.


Nothing wrong with just using a few DMVs either.

Monday, February 21, 2011

On DESKI, Proclarity, and Executive Crystal (Ball) Decisions

Sometimes I wonder whether BI vendors actually use their own tools to look at their market.  If they do, then perhaps they are missing the "sentiment" KPI.

Microsoft lost a bunch of sentiment points by discontinuing BI tools like Proclarity and PerformancePoint planning.  Proclarity as a desktop and dashboard tool met quite a few needs for my clients that aren't filled anywhere else without jumping up price point notches and complexity.  I'm still supporting PerformancePoint, the discontinued flavour.

Now it appears that SAP has taken a similar approach, dropping their desktop client DESKI in favour of their web client WEBI.  Which, of course, has less functionality.  Web apps just don't feel as concrete, physical, or hardened as desktop apps.  Although the technologies are coming together more and more, desktop apps still have points over ease of use and functionality.

How come the BI vendors don't ask their clients how they can serve them better rather than analyzing the P and L for quick-hit cost savings?

IBM (Cognos (formerly SAP (formerly BusinessObjects (formerly Crystal))) developers are an angry bunch!

Am I missing a bracket or two there?

Friday, February 18, 2011

BI in the Cloud or Head in the clouds?

Last week I went to a .NET user group presentation for Microsoft's Azure cloud computing platform.  The topic, though a bit dry, was interesting.  Cloud storage confuses me a bit since I'm a relational database kind of guy.  Azure Cloud Storage provides a basic API to store BLOBs (binary objects like images, music or video) in its massive redundant storage data centers.  It has 3 major types of semi-structured or unstructured storage:
  • Blobs
  • Queues
  • Tables
The coding examples actually offended my sense of good form with databases and coding, probably since the opposite design philosophies are true for Azure Storage apps versus relational database apps.  Or at least this is what I got from the presentation, which might be a bit off.
  • Keys are no longer supposed to be small, integer, incrementing for performance.  
  • Keys are long strings, sometimes with pipe delimiters.  
  • There is no concept of ATOMIC transactions - the app does the work.  
  • A table can hold two different types of object information (invoice/invoice details) with the key differentiating.   Duplicate data is replicated everywhere.  
  • Message Queues have a chance of dropping data which the app needs to handle.  
  • There are limits to the scalability of requests and storage size that the app needs to be aware of and design around.  
  • There's only 1 key on a table, so searching against a non-partition-key field causes table scans.
  • It's better to update / merge data than to append to the end.
The cloud will scale to terabytes, petabytes, exabytes of data depending on your budget, however good luck doing any complex searches against your metadata.  Seems rather painful right now.

Many of the stable, reliable, tried-and-true server and developer tools available outside the "cloud" provide a huge step up in terms of ease of development effort and data quality.  Why are we taking steps backwards in development to accommodate buzzwords and marketing stories?  Is there really a great benefit to moving your enterprise into the cloud?

Cloud in simple words is 'Pay as you use'. Cloud computing is analogous to the way we pay for our utilities like electricity or water based on the consumption. The underlying Infrastructure is owned  and managed by some third party and cost is billed to us in form of units consumed - BI In the Cloud


Driving around eastern Ontario a couple weekends ago, I was amazed by all the farms and houses having solar panels that weren't there last year.  I told my wife some salesperson was doing a good job.  This type of micropower distribution structure seems like the way of the future; not a huge smoke-belching power plant.  Why isn't it the same for the cloud?


The thing that bothered me the most though?  MS has Azure Cloud Data Centers around the world.  But no Azure Cloud Data Centres, eh?  I guess Canada is considered Northern US to the Redmond folks...  :)

Tuesday, February 15, 2011

SAP upgrades its BI tools to 4.0 release

"This release is huge," said Dave Weisbeck, senior vice president of BI and EIM solution management. "Every single tool has had some major upgrades. There's not a single place we haven't touched."

One of my clients I worked with in the past had 2 different versions of their BusinessObjects Universes, with 2 different versions of client and server toolsets running. This was due to the poor migration story BO had, with reports and client tools losing functionality and formatting, a parallel-server migration, and an angry user base (and double the administration) as a result. Hopefully this doesn't happen with the new SAP 4.0 BI tools and there is a clear upgrade path and roadmap.

SAP purchased Sybase last year. Sybase created the original Microsoft SQL product, and MS branched off with their own codebase in SQL 7, further in SQL 2000.  Interesting how many of the BI vendors with a long history (Cognos, Sybase) are being consolidated into the mega software conglomerates.

There may be more than five computers in the world, however it's slowly looking like there's only going to be 5 enterprise BI companies soon..

  • IBM
  • Oracle
  • Microsoft
  • SAP
  • The little guys

Saturday, February 05, 2011

Windows® API Code Pack for Microsoft® .NET Framework

Windows® API Code Pack for Microsoft® .NET Framework provides a source code library that can be used to access some features of Windows 7 and Windows Vista from managed code. These Windows features are not available to developers today in the .NET Framework.

http://code.msdn.microsoft.com/WindowsAPICodePack

Wednesday, February 02, 2011

Office Converters and HTML Viewers

In support of Microsoft’s ongoing efforts to increase the interoperability of its various technologies, we have partnered with Dialogika to create a translator that converts the Microsoft Office binary file formats (.DOC, .XLS, and .PPT) into the Office Open XML standard format (.DOCX, .XLSX, .PPTX).



Enables OpenXML documents to be viewed on any client system in any browser as HTML, and includes an add-ins for Internet Explorer, Firefox and Opera (Windows/Linux)


http://www.interoperabilitybridges.com/projects/openxml-document-viewer


Enables bi-directional interoperability between Microsoft Office (Open XML) and Open Office (ODF) file formats


http://www.interoperabilitybridges.com/projects/openxml-document-viewer