Trying to fit together pieces like network architecture, legacy database design, and growth patterns into the right place can be pretty daunting. Doing it right and seeing the improved performance is satisfying. Not getting it right has a long tail.

For me that’s not a big deal because I have only tinkered with these data types, and am not working on any production applications that use them.

I understand adding support for spatial data types is on the way, but the SQL Azure team will prioritize this feature on the basis of demand.

A short while ago I filled out a form requesting an invitation. At one point I had to gave a brief description as to why I should be included. I wrote a couple of sentences describing my intentions and submitted. The last night the invitation arrived.

I filled out some more information regarding my account and created my first database. It was a little quirky, but I did manage to make a connection to the Azure database from SSMS.

I have been neglecting this blog for a while, but I plan to post a little more frequently as I take a deeper dive into Azure.

And so my appreciation of service oriented architecture had grown beyond an intellectual curiosity. One can take advantage of existing functions and services, stitch them together with your own business logic, and build enterprise class applications with less effort, and lower infrastructure overhead.

A brave new world (well not all that new).

Over the past few months I’ve been working on a data warehouse project that’s been at times both rewarding and exasperating. Today I thought we were nearing completion of the project when several data quality issues jumped up and presented themselves. As I worked through the issues I was struck by the notion that I am encountering business intelligence in its most nascent form.

Until recently a select few people have analyzed data. The data’s quirks and oddities were handled in the brains of those crunching numbers, and not by some formal business process. So with each data issue came an oh-by-the-way moment and new details would emerge. These missing details resulted from people not articulating knowledge they use intuitively.

Imagine you are lending a co-worker your car. You hand over the keys with instructions on where it’s parked. Your co-worker gets to the parking lot and is flummoxed because your car has a manual transmission. The co-worker doesn’t know how to drive a stick shift. You’ve never owned car that has an automatic transmission and the thought never occurred to ask if they knew how to use a clutch. And so it is with emerging business intelligence and data.

As painful as it is sometimes, we are formalizing and standardizing knowledge. This knowledge can now be passed on as personnel changes take place. Years down the road some poor soul is not going to look at a mound of data from 2008 and how wonder how it all fits together.