Ian tells Web 2.0 types to not forget about SQL Server

Augmented Reality 1 Minute

Ian Landsman, who is a Web-based software developer (wrote HelpSpot, a Web-based help desk application), tells people not to forget about SQL Server. Why? Read his words:

“If you need some motivation here’s some. It’s now been 1 week since HelpSpot went live and free trials were available. In that time, 45% of all downloads have been for use with MS SQL Server.”

On the other hand Mike Sanders says it’ll be impossible for Microsoft to get into the new world. Says: “It is pretty clear to me that Microsoft in its present form can not possibly adapt to the changing technological world, since breaking the hierarchy is an integral part of that change.”

David Heinemeier Hansson (the guy who wrote Ruby on Rails) answers my post with: “To be frank, I don’t ever see the good times coming back for them. Microsoft will have to move to higher grounds. Get out of the infrastructure race. Like Apple did.”

John Evans thinks I’d leave to go to work for Google. Hmmm, no, I’m quite happy at Microsoft thank you very much!

That said, if I did leave, it wouldn’t be to work for two kids from Stanford. My wife went to Cal. That just wouldn’t go over in the family very well. 😉

Published by Robert Scoble

I help entrepreneurs build their technology business' story, help with getting ready for investors, with other launch plans, and many other strategic things that can help your new startup. Call to talk: +1-425-205-1921 (text first).

Published

33 thoughts on “Ian tells Web 2.0 types to not forget about SQL Server”

  1. Pingback: » Is Scoble Ruby Off the Rails? Microsoft Weblog

  2. I wouldn’t be surprised to see you leave in 3-6 months mate. If you weren’t leaving, though, it would be because of some major changes inside MS or to your job.

    Either way, I think you’ve outgrown what you were hired for in a big way, so either stuff at work needs to change you’ll eventually get worn down and take a great offer that will help you “change the world” 😉

    Like

  3. I wouldn’t be surprised to see you leave in 3-6 months mate. If you weren’t leaving, though, it would be because of some major changes inside MS or to your job.

    Either way, I think you’ve outgrown what you were hired for in a big way, so either stuff at work needs to change you’ll eventually get worn down and take a great offer that will help you “change the world” 😉

    Like

  16. Why would anyone use SQLServer when PostgreSQL is free (like in beer), works on more platforms, and hasn’t historically been a major security risk?

    No reason that I can see.

    Like

  17. Why would anyone use SQLServer when PostgreSQL is free (like in beer), works on more platforms, and hasn’t historically been a major security risk?

    No reason that I can see.

    Like

  18. Innocent Bystander, that’s not a practical solution for a software vendor. When businesses come to my site and need a help desk solution, but IT only supports SQL Server, should I turn them away and say “hey, rewrite every app in your business to use PG?”.

    There are loads of reasons why a company may have to use a certain DB solution or why they wouldn’t want to support more than one DB platform in their business.

    As a software vendor we need to support what are customers want to use. That’s why HelpSpot supports MS SQL, PostgreSQL, and MySQL.

    Like

  19. Innocent Bystander, that’s not a practical solution for a software vendor. When businesses come to my site and need a help desk solution, but IT only supports SQL Server, should I turn them away and say “hey, rewrite every app in your business to use PG?”.

    There are loads of reasons why a company may have to use a certain DB solution or why they wouldn’t want to support more than one DB platform in their business.

    As a software vendor we need to support what are customers want to use. That’s why HelpSpot supports MS SQL, PostgreSQL, and MySQL.

    Like

  20. Ian – no Oracle?

    Seriously, I’m speaking from the standpoint of someone who needs a database, not someone who is writing an app to sell to people who have databases.

    If you need a database for your own use, pick the open free choice. As for the “support” stuff – I call red herring. You can buy support for Linux, PostgreSQL, whatever if you want to. The reality is that you’ll pretty much never need it. Even Oracle support isn’t a magic bullet and you’ll still end up doing most of the trouble shooting and recovery yourself if you have an incident.

    Like

  21. Ian – no Oracle?

    Seriously, I’m speaking from the standpoint of someone who needs a database, not someone who is writing an app to sell to people who have databases.

    If you need a database for your own use, pick the open free choice. As for the “support” stuff – I call red herring. You can buy support for Linux, PostgreSQL, whatever if you want to. The reality is that you’ll pretty much never need it. Even Oracle support isn’t a magic bullet and you’ll still end up doing most of the trouble shooting and recovery yourself if you have an incident.

    Like

  22. I gotcha, but even from that perspective there is alot that goes into that decision. I think you can make that argument if you’re talking about a person, but with an organization it’s a bit harder.

    For instance, lets say I have an existing payroll system built on SQL Server. Now I’m adding a new billing system we’re building in house. If I choose to go with PostgreSQL (or any other DB), I’ve just doubled my work. I now have to maintain, update, and backup 2 different database systems whereas if I use SQL Server I have no additional work from an IT perspective because my backup and maintenance plans are already in place.

    I know what you’re saying, but I don’t think it’s as clear cut as you might think.

    Like

  23. I gotcha, but even from that perspective there is alot that goes into that decision. I think you can make that argument if you’re talking about a person, but with an organization it’s a bit harder.

    For instance, lets say I have an existing payroll system built on SQL Server. Now I’m adding a new billing system we’re building in house. If I choose to go with PostgreSQL (or any other DB), I’ve just doubled my work. I now have to maintain, update, and backup 2 different database systems whereas if I use SQL Server I have no additional work from an IT perspective because my backup and maintenance plans are already in place.

    I know what you’re saying, but I don’t think it’s as clear cut as you might think.

    Like

  24. “If you weren’t leaving, though, it would be because of some major changes inside MS or to your job.”

    Let’s hope it’s because of major changes inside MS.

    Microsoft needs more objective employees like Scoble.

    Like

  25. “If you weren’t leaving, though, it would be because of some major changes inside MS or to your job.”

    Let’s hope it’s because of major changes inside MS.

    Microsoft needs more objective employees like Scoble.

    Like

  32. Ian,

    I’ve run quite a number of IT departments. SQL server would never get into the door as its a single platform solution and I like options. Oracle, Postgres, mysql (maybe – transaction support is a bit new), even Sybase will garner serious consideration. SQL Server will not.

    Also, you’ll still have 2 databases – 2 SQL server instances, 1 SQL server and 1 Postgres, doesn’t matter much. Its not zero work to care for an extra database.

    Like

  33. Ian,

    I’ve run quite a number of IT departments. SQL server would never get into the door as its a single platform solution and I like options. Oracle, Postgres, mysql (maybe – transaction support is a bit new), even Sybase will garner serious consideration. SQL Server will not.

    Also, you’ll still have 2 databases – 2 SQL server instances, 1 SQL server and 1 Postgres, doesn’t matter much. Its not zero work to care for an extra database.

    Like

Comments are closed.