Can I Install SQL Express on SBS 2008 Std.?

Discussion in 'Windows Small Business Server' started by Bob Smedley, Mar 22, 2010.

  1. Bob Smedley

    Bob Smedley Guest

    I have a standard version of SBS 2008 (64-bit). SQL is installed by default
    for SBSMonitoring and other services. I'd like to be able to use this copy
    of SQL to host one of my own tables. I need to be able to connect to the
    database from one of my desktops in my network. When creating a System DSN
    to make the connection it returns server not found or permission denied. I'm
    using windows authentication for the DNS. I am able to manage the SQL
    instance when logged into the server itself but not remotely from the

    Is not possible or am I doing something wrong?

    The version of SQl shown in the Add/Remove shows 2005.

    Bob Smedley, Mar 22, 2010
    1. Advertisements

  2. Download and run the SQL Express installer. You'll be creating another
    database instance. I'd *strongly* discourage you from attempting to add your
    own tables and data to the existing SBS internal instance.

    Cliff Galiher - MVP, Mar 22, 2010
    1. Advertisements

  3. Bob Smedley

    Bob Smedley Guest

    OK,. I was thinking of doing that but wasn't sure if it would mess up the
    default sbsmonitoring service.


    Bob Smedley, Mar 22, 2010
  4. Russ SBITS.Biz [SBS-MVP], Mar 22, 2010
  5. An additional instance will not mess up an existing instance. However,
    please remember that you will need to setup independent backup
    procedures for your new instance.

    SQL Express 2008 is easy to add and easy to manage with SQL management
    studio. Consider giving it a descriptive instance name to make it easier
    to find. It is possible to have both SQL 2005 and 2008 co-exist on the
    same server.
    Leonid S. Knyshov
    Crashproof Solutions
    Twitter: @wiseleo
    Microsoft Small Business Specialist
    Try Exchange Online
    Please vote "helpful" if I helped you :)
    Leonid S. Knyshov // SBS Expert, Mar 22, 2010
  6. Yes, but to keep things simple IMO just create a new instance.
    It's not like you are going to have that many on a SBS2008 server anyway
    If so you'd want to build a server just for it IMO
    You can always Add more Memory or Tweak the SQL usage.
    (This is one reason why I also like dual Proc servers, flexibility in

    Russell Grover - SBITS.Biz [SBS-MVP]
    Small Business Server/Computer Support - www.SBITS.Biz
    Question or Second Opinion -
    BPOS - Microsoft Online Services -
    Russ SBITS.Biz [SBS-MVP], Mar 23, 2010
  7. No. SQL caches by default, so when data is accessed, SQL caches that data
    in memory for faster reads and writes. Since the *DATA* causes more memory
    usage, it doesn't matter if that data is consolidated under one instance or
    spread out across'll still be cached and still take up memory.

    Yes, there is *some* overhead for managing multiple instances, but the
    management overhead is comparatively small compared to the overall SQL usage

    Cliff Galiher - MVP, Mar 23, 2010
  8. Russ SBITS.Biz [SBS-MVP], Mar 24, 2010
  9. Fair enough. The no was a "practical" answer in that there is not a
    *significant* memeory usage difference between instances and databases.
    And, in fact, I'd argue that separate instances is better because some
    memory settings can only be set at the instance level, and the 4 gig limit
    is set at the instance level for SQL Express.

    But the answer is "yes" on a technical level as there *is* overhead for
    managing separate instances.

    So no *and* yes, depending on if we are discussing practical vs technical.
    And yes, I should've made that more explicitly clear.


    Cliff Galiher - MVP, Mar 24, 2010
  10. that's why my answer was the yes but
    the but was my no :)


    Russell Grover - SBITS.Biz [SBS-MVP]
    Small Business Server/Computer Support - www.SBITS.Biz
    Question or Second Opinion -
    BPOS - Microsoft Online Services -

    Russ SBITS.Biz [SBS-MVP], Mar 24, 2010
  11. Keep in mind that the articles you linked to are:

    1) Primarily dealing with SQL Server, not SQL Server Express. There is a
    *significant* difference between two database instances using two different
    tempdb files when these databases have millions of records spanning hundreds
    of gigs getting accessed hundreds of times *per second* and....well...*any*
    database in an SBS network.

    2) Some of the responses in those articles are written by old-school SQL
    Server users. There was a time when SQL server was the poor little brother
    of the other databases and did suffer some serious optimization issues. It
    lagged significantly behind Oracle *and* IBM's DB2 in this regard. This
    hasn't been the case for many years, but like anybody in technology, some
    old knowledge still lingers and people try to apply old rules to areas they
    no longer apply to. Windows 7 does *not* have a 640k memory barrier...

    In my (not so) humble opinion, messing with the SBSMonitoring instance is
    like messign with the default SBS group policies. You can do it if you
    *REALLY* know what you are doing, but by and large, I'd *strongly* encourage
    creating new group policies and separate database instances. It is
    exceedingly rare that the latter will get you into irreversible trouble, and
    even more rare that there is a legitimate benefit to the former. for thought.


    Cliff Galiher - MVP, Mar 24, 2010
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.