SQL Server 2008….Finally

imageI've been hanging out with Ed Katibah in San Diego at the ESRI User Conference and not in the whole two days we stood in our circular booth did he mention this was going down tonight, but whatever Ed! Actually, the booth was so busy, we spent all of about 5 minutes catching up. I digress. After waiting through CTPs, SQL Server 2008 is finally locked down and released to manufacturing. The press release is out - Microsoft Releases SQL Server 2008. Why do I care? Better question, why should you care? Because, there's are significant spatial index, algorithms and support included natively in the release (also included in SQL Server Express) - see the Spatial Data page for details. What happens when you connect a spatial database with Virtual Earth? You get Microsoft Geospatial. If you're interested in ripping out your current spatial database and mapping system, I'm not sure there's a better time to spend a few R&D hours to investigate the possibilities and cost savings associated with this release. Hopefully, we'll see Ed putting something on his blog. At the very least, Johannes Kebeck has some great examples of Virtual Earth + SQL Server. I suppose I should too. Or, check out the SQL Server Community pages on Technet.

Here are the key dates to be aware of:


Comments (6)

  1. I think they are just teasing us.  I tried to install the developer edition and it said visual studio sp1 needs to be installed first.

  2. nukegold says:

    Will the Express or Compact versions support spatial features?

  3. Chris Pendleton says:

    Pkellner – Looks like there are some issues with installing RTM until VS 2008 SP1 is released – http://support.microsoft.com/kb/956139.  


  4. Chris Pendleton says:

    Hey Nuke,

    Express will include spatial features. SQL Server Compact Edition (CE) is a different code base, on a different development schedule than SQL Server 2008.  Consequently, SQL Server CE, will not have any spatial features this go around (a new version came out about a year ago).


Skip to main content