Options
error
Brian Donahue
Posts: 6,590 Bronze 1
Hi,
Good news! I guess that explains how sysobjects kept getting out of
synch.
Brian Donahue
Technical Support
"Don" <don_nguyen@scantron.com> wrote in message
news:gH6cxagJDHA.1424@server53...
> A few weeks ago I posted this problem:
>
> >Hi,
>
> >We've been using SQL Compare for quite some time. Lately, we've been
> getting
> >this error:
>
> >Error Loading database [SERVERNAME.DBName]
> >Error Scripting Tables
> >Error scripting Table [TableName]
> >[SQL-DMO] The ID '13641986' was not found in the Tables collection.
>
>
> After fiddling around with why this was happening, we've figured it was
due
> to a table being deleted while in the middle of scripting out a database,
in
> between the time the list of tables is generated and the time it comes to
> script out the deleted table. We're guessing the same things would happen
> if stored procedures, or views were deleted in the middle of the
> registration.
>
> We found a job that was dropping and recreating a table every 5 minutes
that
> caused the problem. Hope this helps anyone that might run into this
problem
> later.
>
>
>
> Don
>
>
Good news! I guess that explains how sysobjects kept getting out of
synch.
Brian Donahue
Technical Support
"Don" <don_nguyen@scantron.com> wrote in message
news:gH6cxagJDHA.1424@server53...
> A few weeks ago I posted this problem:
>
> >Hi,
>
> >We've been using SQL Compare for quite some time. Lately, we've been
> getting
> >this error:
>
> >Error Loading database [SERVERNAME.DBName]
> >Error Scripting Tables
> >Error scripting Table [TableName]
> >[SQL-DMO] The ID '13641986' was not found in the Tables collection.
>
>
> After fiddling around with why this was happening, we've figured it was
due
> to a table being deleted while in the middle of scripting out a database,
in
> between the time the list of tables is generated and the time it comes to
> script out the deleted table. We're guessing the same things would happen
> if stored procedures, or views were deleted in the middle of the
> registration.
>
> We found a job that was dropping and recreating a table every 5 minutes
that
> caused the problem. Hope this helps anyone that might run into this
problem
> later.
>
>
>
> Don
>
>
This discussion has been closed.
