SQL Express vs SQL Full

4 posts, 0 answers
  1. Dan
    Dan avatar
    2 posts
    Member since:
    Jan 2009

    Posted 05 Jan 2009 Link to this post

    I notice that in the install of the ORM Express, we can choose our DB instance, and it "seems" to allow (local) (which is my SQL full) as well asl the (local)/SQL Express for the sample database. That's somewhat confusing to me, as the posting on your site states that the ORM Express is only supposed to work with the "free" database servers.

    What are the effects of attempting to install it with the full SQL version? Does the sample database work?

    Thanks for any clarification.
  2. Thomas
    Admin
    Thomas avatar
    590 posts

    Posted 08 Jan 2009 Link to this post

    Hello Dan,

    there is the distinction between the normal SQL server and its express edition. Maybe you got confused and used the database from the other without noticing. Technically, we check upon connection, but afterwards the ORM behaves in the same way.
    The effect will only visible once you try to open the database with your persistent classes. You can check if the opening would succeed by looking at the VS OpenAccess menu Help->Product Info. There you will find an indication which version is found (developer or express).
    The sample databases could also get deployed to the normal database server; again, this is a licensing issue and not a technical problem.

    Kind regards,
    Thomas
  3. DevCraft banner
  4. Dan
    Dan avatar
    2 posts
    Member since:
    Jan 2009

    Posted 08 Jan 2009 Link to this post

    Hi Thomas,

    Thanks for the reply!

    I'm wondering if you're making a distinction in the type of connections made between SQL Express and SQL Full:

    1) SQL Express allows a "dynamic" connection to a database file. But SQL Express can run a "regular" connection that involves a permanent attachment to an .mdf.
    2) SQL Full cannot do the dynamic connection to a database file: all databases served by the full version of SQL must be attached to the SQL server.

    So, when the ORM makes the connection, how does it make the distinction about the server it's attaching to? Or is it making the distinction based on the connection string (the "dynamic" file connection)?

    Thanks for any insight on this!
  5. Thomas
    Admin
    Thomas avatar
    590 posts

    Posted 09 Jan 2009 Link to this post

    Hi Dan,

    the technique is to ask the server what kind of server it is. So we open the connection with the info provided and reject later when we find a non-express server used by an express licensed client.

    Kind regards,
    Thomas
Back to Top