SQL Server Express 2005

On Monday November 7, 2005, Microsoft released the latest version of its SQL Server product. There are numerous licensing configurations but perhaps the most notable was SQL Server Express (http://msdn.microsoft.com/vstudio/express/sql/default.aspx).

I say it’s notable because it’s free. Here’s a feature comparison across licenses:
http://www.microsoft.com/sql/prodinfo/features/compare-features.mspx

What’s interesting about this strategy is that Microsoft appears to be acquessing to the MySQL open source bandwagon by allowing a personal edition version of SQL Server to be distributed free of licensing. The Express version is a single-processor-aware application with a 4GB max container size – perfect for small business computing – with tuning and tSQL.

This would appear to be a replacement to the SQL developer engine and would be another nail in the coffin for JET (the dbase engine that runs Microsoft Access’ *.mdb proprietary file access). Not only would the SQL engine provide more robust DBMS processing, but it would allow lightweight Microsoft Access applications to finally become HIPAA compliant (transactions in JET cannot be audited to user accounts, creating a Security Rule violation).

Noteworthy if anyone does any development with Access, we may be looking at the product that may eventually become bundled with Office as its transaction processing engine.

R
www.micklerandassociates.com

The Not-for-Profit Technology Plan

The not-for-profit has a vested interest in deploying technology to better internal business processes, increase efficiency, leverage economies of scale, and reduce operating expenses. However, non-profits are under exceptional pressure to justify spending that doesn’t directly relate to their cause, and IT could be perceived as a risky investment in rapidly obsoleting assets. So the challenge becomes a management problem: how to transparently relate technology spending to the strategic business plan.

Traditionally, this is accomplished through a written document called a Technology Plan. Usually a consensus-driven document, the Technology Plan articulates the role of technology to meet the organization’s objectives and describes the upcoming strategy for acquisition and deployment. It’s a blue-print document that can then be shared with stakeholders to explain technology spending in conceptual terms and often predicates short-run budget requests.

In researching this topic for a presentation to one of my graduate classes, I came across information for preparing technology plans for non-profits. I thought it would be useful to capture them here.

R
www.micklerandassociates.com