Post reply

CHECK CONSTRAINTS

  • September 2, 2005 at 8:23 am

    #110609

    CHECK([EXTRACT_DATE] >= '12/29/2002' and

    [EXTRACT_DATE] <= '2/1/2003 23:59:59.997')

    CHECK([EXTRACT_DATE] >= '2/2/2003' and

    [EXTRACT_DATE] <= '3/1/2003 23:59:59.997')

    and SO ON...

    ERROR:

    UNION ALL view 'ARCH_SAP40' is not updatable because a

    partitioning column was not found. [SQLSTATE 42000] (Error 4436).  The step failed.

    If I drop all the CKECKS and RECREATES all of them it worked before but now again it failed.

    Is there a better way to define the above CHECK CONSTRAINTS

    Jagan

  • September 2, 2005 at 8:27 am

    #587228

    Do you have the primary key(s) of the table you want to update in the view??

  • September 2, 2005 at 8:32 am

    #587232

    EXTRACT_DATE is part of PK.

  • September 2, 2005 at 8:39 am

    #587242

    Is part of... what are the other keys? Are they also in the view??

  • September 2, 2005 at 8:39 am

    #587241

    No we don't modify PK values.

    Jagan

  • September 2, 2005 at 8:41 am

    #587243

    Extract_Date+Order_No+Line_No is the PK but Extract_Date is the only Check Consraint. All Columns in all the Tables are part of view with UNION ALL.

  • September 2, 2005 at 8:44 am

    #587246

    It takes the WHOLE PK to trace back to the correct row and do the update. Access works in the same way and I don't see how sql server could do it any differently.

Viewing 7 posts - 1 through 6 (of 6 total)

You must be logged in to reply to this topic. Login to reply