Professional Web Applications Themes

cursors and schema chage error -- Msg 16943 - Microsoft SQL / MS SQL Server

The following error gets throws during a cursor operator about 2% of the time this code runs in production. We have never seen it in our lab. To our knowledge there is no schema change going on. Could this error actually mean something else? 'Msg 16943, Sev 16: Could not complete cursor operation because the table schema changed after the cursor was declared. [SQLSTATE 42000]'...

  1. #1

    Default cursors and schema chage error -- Msg 16943

    The following error gets throws during a cursor operator about 2% of the
    time this code runs in production. We have never seen it in our lab.

    To our knowledge there is no schema change going on.

    Could this error actually mean something else?


    'Msg 16943, Sev 16: Could
    not complete cursor operation because the table schema changed after the
    cursor was declared. [SQLSTATE 42000]'


    jlongino Guest

  2. #2

    Default Re: cursors and schema chage error -- Msg 16943

    Disabling/enabling triggers and constraints also count as schema changes, so
    that is another possibility.

    --
    Jacco Schalkwijk MCDBA, MCSD, MCSE
    Database Administrator
    Eurostop Ltd.


    "Russell Fields" <com> wrote in message
    news:phx.gbl... 
    dropping 
    >
    >[/ref]


    Jacco Guest

  3. #3

    Default Re: cursors and schema chage error -- Msg 16943

    Could this be related to tion in any way?
    Does adding a publication or more likely a subscription make any changes
    that might be considered a schema change?

    I don't think we have any "data loading" (I assume you mean bulk loads)
    going on, but changes to triggers and or constraints might be posible.



    "Jacco Schalkwijk" <co.uk> wrote in message
    news:uFxA#phx.gbl... 
    so 
    > dropping [/ref][/ref]
    the [/ref][/ref]
    the 
    > >
    > >[/ref]
    >
    >[/ref]


    jlongino Guest

  4. #4

    Default Re: cursors and schema chage error -- Msg 16943

    tion will cause schema changes under certain cirstances. Merge
    tion will add a rowversion column to all the tables that are
    published and create triggers on them. Snapshot publication I think will
    not, although I am not totally sure. Adding a subscription to a publication
    will only cause changes in the distribution database, so I don't think that
    will be the cause.

    --
    Jacco Schalkwijk MCDBA, MCSD, MCSE
    Database Administrator
    Eurostop Ltd.


    "jlongino" <com> wrote in message
    news:phx.gbl... [/ref]
    changes, 
    > > dropping [/ref]
    > the [/ref][/ref]
    lab. [/ref]
    > the 
    > >
    > >[/ref]
    >
    >[/ref]


    Jacco Guest

Similar Threads

  1. Replies: 1
    Last Post: June 28th, 09:16 AM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139