SQL Azure does not support NEWSEQUENTIALID(), so "Update Database From Model" wizard should not suggest it.

Thread is closed for posting
2 posts, 1 answers
  1. Jacek
    Jacek avatar
    31 posts
    Member since:
    Sep 2011

    Posted 10 Apr 2012 Link to this post


    When you change Identitiy Mechanism for Guid column to DatabaseServerCalculated, the "Update Database From Model" wizard generates below script

    ALTER TABLE [documents] ADD CONSTRAINT DF_Documents__document_id DEFAULT (newsequentialid()) FOR  [_document_id]

    However, newsequentialid() is not supported by SQL Azure (at least not yet).

    (In model settings backend is set to Microsoft SQL Azure, OA v2012.1.329)

    Not a big deal, but it made me think: what impact does this setting of the type of backend have on overall interface? 

  2. Answer
    PetarP avatar
    754 posts

    Posted 11 Apr 2012 Link to this post

    Hello Jacek,

     You are correct and this is indeed a bug on our side that we have fixed now. The fix for this will be available with our next internal build/service pack. From now on we will be using newid() instead of newsequentialid().

    This should not have any impact on your application as currently ddl script is created only for identities of type integer and guid. What this setting does is simply notifies our runtime that this ID will be generated by the database so that it is omitted in the sql statement we generated during inserts.

    Please find your Telerik points updated for sharing this bug with us.

    the Telerik team
    Telerik OpenAccess ORM Q1 2012 release is here! Check out what's new or download a free trial >>
Back to Top