Stories from the Field
In addition to looking at different deployment scenarios, I wanted to talk to someone with extensive non-Microsoft experience that ended up choosing SQL Server as a primary platform. So I talked with Vishwenath Kizhapandal, Chief Operating Officer, iLink Systems. After a decade developing custom apps with Java and open source tools, iLink, now a Microsoft Gold Partner, made the switch to Microsoft solutions two years ago. We talked about specific apps he's worked on and why SQL Server gave iLink more power, more flexibility, and as a result, more opportunities.

The Problem Is Not the Snow
While many articles offer a direct comparison of free databases, such as MySQL to SQL Server Express to DB2 Lite, Kizhapandal says, "It would be unfair to compare just the database without comparing the overall development cost.

"You don't typically have a solution with just a database alone. You're always building an app which leverages database technologies. [For example] if your app needs good reporting, what's the point of having data collected if you can't report on it?" iLink customers need the advantages of a full-featured development environment, not just reporting but triggers, stored procedure debugging, and other features. While MySQL added new support for some of these features in version 5.0, other important features are only available through third-party tools.

Meanwhile, Microsoft integrates programming and business intelligence tools through the entire stack. For example, you can call a stored procedure from an ASP.NET page, step into the procedure, and debug line by line. On one occasion, "it took less than a month to put together a dashboard using the Developer Edition, something not that easily possible with MySQL."

"People don't realize, they're trying to save a few thousand in licensing costs, and end up creating several thousands in development costs."

Kizhapandal likens it to a recent drive through Seattle in the snow. "It wasn't the snow, it was the other drivers who were the problem."

A Full-Blown Database in the Field
Using the Express and Developer Editions of SQL Server lowers development costs even further while not limiting future deployment. Says Kizhapandal, "We built a distributed app for one of our clients—a centralized server with field-based clients. Clients had a need for storing the data and syncing with the central server. Problem: if we used SQL Server [Standard Edition], client costs would've been prohibitive. Instead we used MSDE [Microsoft SQL Server Database Engine, the precursor to SQL Server Express]. The central server had to have pretty complex needs, but we already had the Developer Edition of SQL Server, so we could take full advantage of the .NET development environment. Then, when we deployed, all we needed on the client was the MSDE engine." iLink initially developed the app on MSDE a couple years back, before SQL Express was available. "But since we had developed the whole app using existing development tools we could easily convert to SQL Express, which we're doing now. MSDE had some limitations but SQL Express has removed connection limitations and other limits in MSDE. Now clients have full-blown database." Database size is limited to 4GB, of course. But field clients don't need to store more than that, so the limitation doesn't present a problem.

More than Mobile-Ready
As mentioned already, SQL Server CE, formerly SQL Server Everywhere, formerly SQL Server Mobile, gives developers a low footprint solution for mobile devices. While MySQL also has a small footprint, Kizhapandal says it's important to keep in mind that "no one develops just a mobile app alone. Most of them are part of an app family. We have a product suite with desktop apps, enterprise apps, and mobile apps that have to talk with the other apps to upload data. Previously, you developed either flat database apps or apps that talked over the server to store data. Now, you store data locally, then sync data when you have better connectivity.

"This is where the CE Edition comes into play. It has a small footprint, but that's not the biggest benefit. This is a complete database. When deploying, you just take the database and bundle it into the app. When you develop the app, you are developing in a full-blown SQL Server edition. You have the ability to take the same exact database and drop it into the mobile device."

Prototyping with Potential
"It's also true that if you're trying to do proofs of concept, it's tempting to go MySQL because you don't need approval or budget from the boss. But even there, it doesn't make sense—you're not going to be developing proofs with more than 4G data, so use SQL Express. And once you do the pilot and your clients see it work, you don't have to rebuild it in SQL Server.

"We do a lot of prototyping and proofs of concept, for example showing WPF [Windows Presentation Foundation] technologies for our clients to help them understand the power behind user experience. You can't demonstrate that except by building the UI and letting them play with it."

Similarly, "we also do proofs with the BI stack because not a lot of people understand what they can get from their data using business intelligence until you show them. For example, we built a small 15-line KPI [Key Performance Indicator] for one of our insurance clients. Once we deployed it in the BI stack, they were able to see the charts and graphs. We did a larger project for them after that."

"I Grew Up."
I asked Kizhapandal about the intense loyalty some MySQL-only developers feel for their chosen platform. He had this advice for other ISVs and start-ups. "They need to be able to understand the user metrics. This is more important than just storing data and just using a shopping cart. If you understand your users today, you'll be able to do more in the future. Are you just storing data or are you trying to understand your business?"

He says, "I was in the Anything-But-Microsoft crowd. The simple answer is, I grew up. Once you understand you're trying to solve business problems, not technical problems, you'll get it."

Where to Go from Here
While SQL Server has long been positioned as the optimum solution for enterprise-level apps, developers often disregard its applicability to other market tiers. If nothing else, developers at mid-level ISVs should consider SQL Server for prototypes, Web apps, multi-platform apps, or any scenario that require versatility, portability, and scalability on the part of the database. ISVs who want to expand their potential customer base by switching over from MySQL might also look at available migration assistance.

For instance, the SQL Server product team has released a migration tool called the SQL Server Migration Assistant. Current versions cover Access, Oracle, and Sybase migration.

Also, Microsoft's NXT program helps ISVs at all tiers migrate their products to SQL Server. Companies with less than $5M in revenue benefit from complimentary licensing and MSDN subscriptions, instructor-led training, and Microsoft Partner Program benefits. ISVs with over $5M in revenue gain additional benefits, like funding, delivery partner services, and marketing support for their new solutions.

Here are a few more resources to check out:

• SQL Server 2005 Product Comparison Chart
• More on SQL Server 2005 Express Edition
• The SQL Server Express Toolkit
• NXT Funding Benefits for ISVs
• NXT Technology Justification

* This article was commissioned by and prepared for Microsoft Corporation. This document is for informational purposes only. MICROSOFT MAKES NO WARRANTIES, EXPRESS OR IMPLIED, IN THIS SUMMARY.