SQL Server Express – Initial thoughts (by yag)

Man, blogging is addictive. I'm supposed to be paying attention in this session... <g> Anyway, wanted to note a few things about SQL Express because I haven't seen a lot about this online yet - though I expect that to change.

First - some of the capabilities:

  • Support for XCopy style deployment
  • No workload governor
  • Support for databases up to 4Gb in size
  • Support for up to 50 instances
  • Only supports 1 processor
  • Only supports 512 Mb of RAM

So - what we have here is a version of SQL Server that runs on your local machine - growing up to 4 gig. The XCopy deployment is also awesome. Instead of attaching/detaching the MDF, you'll be able to XCOPY the database to a new machine that has SSE running, and then just attach via the file path. Very easy deployment. Hooking that in with the new Click Once stuff in VS2005 is awesome. Deploy your winforms app securely and simply - including its database.



Comments (13)

  1. Hey man!

    You stole my list! 😉



  2. yag says:

    Yeah, yeah, yeah, Brian. <g> I noticed that your entry is almost an hour before we opened up the info. <g>

    For those who may not realize this – Brian and I are sitting side by side here in Amsterdam, typing blog comments at each other. <g> Pretty hopeless…

  3. Server clock is wrong! I was framed! I was framed. 😉

  4. When you say ‘Only supports 512 Mb of RAM’ do you mean it only installs on machines with 512mb or less or that it only uses 512mb for itself (I assume the latter)

  5. Lance Delano says:

    He means that it only uses 512 mb for itself.

  6. Ron Green says:

    Developer Center says it supports 1G of RAM.

  7. Alex Kazovic says:

    Does this mean that MS Access will in the next version use this instead of Jet?

Skip to main content