Unless you’re a weatherman, a cloud will remain just a cloud

In the last few years we must have heard every way there is to describe an IT cloud: private, public, federated, hybrid, government, open source etc. etc..  Although there are several cloud delivery models (public, private, hybrid) and several cloud service models (SaaS, PaaS and IaaS), ultimately clouds are a concept, a style, or perhaps even a design pattern. 


Public + On-premises = Hybrid

Right now, we’re starting to see the vendors and analysts are planning for most of us to be using public cloud services in the near future.  We’ve heard that story for a few years but what’s changed is that we are about to start transparently integrating them with what we do in our own data centres, and think nothing of it

A Gartner survey for example has recently found that 70% of the companies asked will be adopting a hybrid cloud strategy by 2015, while both Oracle and Microsoft are making their on-premises products seamlessly integrate with public cloud services.  In fact, this week Microsoft have put their foot down really hard on the “hybrid cloud” pedal. (“New Hybrid Cloud Capabilities and Enhancements” from http://blogs.technet.com/b/dataplatforminsider/archive/2013/10/17/sql-server-2014-ctp-2-now-available.aspx)


Did we ever realise we now have private clouds?

We heard a lot about private clouds, especially how they could extend the value of a virtualisation platform to provide self-service and on-demand application services etc.  However, this is one example where I think the technology has overtaken the marketing messaging.  Increasingly, today’s enterprise virtualisation infrastructures are very close to what were described as private clouds only a year ago ago, we’ve just never fully adopted the term. 


What will we use hybrid clouds for?

What I see happening though is the borderlines between on-premises and public cloud services blurring for most people in the next 18 months. 

My expectation is it’s going to become normal for most to have some disaster recovery, offline storage, complex logic computation or burst capabilities for on-premises systems using public IaaS or PaaS services.  (I’ve ignored the fact that most people are already using SaaS today, even if its just for email etc.)

I think it’ll also become normal to have our development platforms for our mission critical on-premises systems on a low cost public cloud  platform.  The two platforms might be used in different parts of our infrastructures or application lifecycles, but I suspect the names private and public cloud will feel too technical and disappear from general use.  We may replace them with the terms internal and external but they’ll all be part of our hybrid cloud. (http://www.gartner.com/it-glossary/hybrid-cloud-computing)


My guess is we’ll even drop the word hybrid and just have “a cloud”

I suspect we’ll never adopt the word hybrid en-masse.  As always, we’ll use the right tool for each task regardless of whether it comes from our public or private clouds, but in the same way we use virtual and physical services today without thinking twice about how they’re delivered, the same will happen with cloud services.  We’ll just have “a cloud”, our cloud.


Quick links to what’s new in SQL Server 2014

Below is a set of links or updates from Microsoft’s “what’s new” web pages for SQL Server 2014.


Features per Edition



Database Engine




“SQL Server 2014 has not introduced significant new features to SQL Server replication.”
“SQL Server 2014 does not support replication to or from SQL Server 2005 or SQL Server Compact.”


Analysis Services



Integration Services

“SQL Server 2014 Integration Services is unchanged from the previous release.”


Reporting Services

“SQL Server 2014 Reporting Services is unchanged from the previous release.”

Learning by reading things I don’t understand

In the age of Twitter, LinkedIn groups, Google Plus and the rest, I still read blogs as RSS feeds in Outlook.  I only read about 20 so that’s why it might be easier for me to use Outlook than newer methods.


I really was reading the same blogs as I was last year

A lot of my RSS subscriptions are to blogs by some leading technical authors in my technical space.  They’re still very valid and relevant to what I do but I realised a few months ago they bought too much comfort and not enough long term personal development.  In fact, my list of RSS subscriptions hadn’t changed much in a couple of years.

My realisation was that to learn half a dozen new things, I was having to read two dozen articles.  Reading wasn’t an efficient use of my time like it used to be.


The less I understand, the more I learn

In recent months I’ve expanded the list of blogs I read to include those I want to understand but today do not always understand.  In actual fact, what I’ve done is flipped the numbers I mentioned above around: I’m now learning two dozen things from every half a dozen articles I read.  I’m making learning easier, by reading harder materials.


What am I now reading?

What surprised me when I started looking for less technology specific IT architecture blogs was that I didn’t have to look very far.  In fact, all of the personal rather than commercial architecture blogs I now read are all either on Microsoft’s MSDN or TechNet web sites.  It’s reassuring for now that I didn’t have to dive straight into the TOGAF or COBIT communities to start finding new gems.


The blogs I now also read

Below are links to the blogs I’ve started reading recently.  Some don’t have new materials published very often, but when they do….etc. etc..

So here are the links:






A conversation with a CxO


Recently, I’ve had some short conversations with CxO stakeholders that made me remember they can be very different to those I’m used to.  I wrote these notes that I thought I’d share.

Introduce yourself in one line

Start the conversation by saying in one line what you’re there to do in a way that they’ll understand.  Be confident and specific about what you personally are doing for their organisation. 

The first thing they’re probably thinking is who is this person and why do they want to speak to me.  Get that concern out of their head from the moment you start talking.

Prepare topics not questions

Have a list of two or three main topics you want to discuss as you’ll find it hard to ask specific questions or get the type of answer you wanted to a specific question if you do.

Your topics might be: your priorities, your challenges, industry trends, or your success measurements.

Expect them to do 99% of the talking

Time with them is valuable because their time is valuable to their organisation, so don’t waste conversation minutes by asking long questions or saying more than you need to.

They also like talking lots because they’re considered an important opinion and are used to having to share it.  Enjoy the fact they’ve chosen to want to talk to you, and are.

Remember keywords not details   

It’ll be difficult to take notes during the conversation.  Lots of things will be said in a short space of time, too much for you to write notes as the conversation progresses.

Instead, remember keywords to write down immediately after the conversation, such as simplification, standardisation, new leadership, or new markets. 

If you really must take away something very specific, like the name of someone they suggest you speak to, pause the conversation while you make sure you write down the correct name.  But I’d only allow myself to do this once, at the most twice.

Enjoy it

Be relaxed, natural and yourself when you meet with them.  Too much of their day will feel like it’s filled with people they don’t want to meet, make them glad they chose to meet with you.

Re-focussing my blog

My blog is almost three years old now and over that time the number of posts I’ve written has gone from several per week to none per month, the latter being the most common.

The Past

I’ve realised this weekend this was because I’d set myself too narrow a subject area, mostly SQL Server, and got to the stage of never feeling comfortable writing something less than a magazine article.  As a result, I felt a bit guilty reading lots of other blogs but not even writing content that people could choose to ignore, let alone read.

The Future

This weekend, I decided to start sharing much more of my professional interactions with information and start blogging again.  The difference being I’m not going to limit my posts to just things related to SQL Server, or even Microsoft products, or even software.  These days for every technical article I read, I probably read nine non-technical articles.  I still learn lots, that’s why I’m looking forward to sharing more.

Consequently, I’m looking forward to writing again.

October 2013

UPDATED: Windows Server 2012 Failover Clustering

Back in January, I wrote a blog article about some issues I faced when installing SQL Server 2012 failover cluster instances on Windows Server 2012, it’s available here.

Since then, I’ve seen some of the same error messages re-occur in other situations and they always made me think they were more related to Active Directory more than SQL Server.

The good news is that some of these Windows errors now have hotfixes for them, meaning they’re acknowledged as being Windows Server 2012 related, rather than issues with SQL Server.

Microsoft now have a “Recommended hotfixes and updates for Windows Server 2012-based Failover Clusters” web page that is getting regularly updated.

The link to the page is here http://support.microsoft.com/kb/2784261

There are currently six hotfixes listed, of which two are related to some of the errors I wrote about in January.

Architects and Architectures

In the last few months I’ve been presenting a new session at community events that’s had a positive reception that I’m pleasantly surprised at.

It’s had several titles, but currently its “How to be a more successful architect” and I originally created it as an overview of my Microsoft Certified Architect journey, although I’ve taken it on a different course since then.

Hopefully of interest to everyone

The session is hopefully interesting to everyone in the IT industry, not just a specific type of SQL Server professional.  It’s foundation is the idea that regardless of your job title, you’re probably informally, or formally, performing the role of an architect at some point in your working day.

It could be you have to clarify someone’s requirements so you can understand how whatever you create for them demonstrates its value the most.  Or, you could you to justify to someone, or yourself, why the solution design you’ve come up with is the right design as you’ve taken a structured path to designing it.


Presentation slides

The slides from my most recent delivery of the session at SQLSaturday #194 in Exeter are available here.   Like all architectures its evolving, so I’m sure there’ll be newer versions in the future.


Presentation links

Within the presentation, and during my delivery of it, I mention numerous online resources that I recommend reviewing as you develop your IT architect skills.


Architect Certifications

Global IT Architect Association’s CITA-P here.

The Open Group’s Certified Architect here.

Microsoft’s Certified Architect here.

Architect Resources

Microsoft’s The Architect Journal here.

Perspectives Based Architecture for requirements gathering here.

ATAM for prioritising requirements here.

Waterfall vs. Agile methodologies here.

Influencing Without Authority book here.

MSDN Patterns and Practices library here.

Microsoft Application Architecture Guide here.

Solution Lifecycle Management

ITIL Application Life Cycle Process here.


Hopefully something somewhere in this post or the web links has caught your imagination, in which case, please share just what in the comments section.


Get every new post delivered to your Inbox.