registering database
Brian Donahue
Posts: 6,590 Bronze 1
Hi,
We've covered the possibilities that SQL DMO needed to be re-installed,
checked the database with DBCC, and did some queries to sysobjects looking
for these table objectIDs with no success.
Does anyone out there in DBA Land have any suggestions as to why SQL DMO
is being so naughty?
Brian Donahue
Red Gate Support...
"Don" <don_nguyen@scantron.com> wrote in message
news:Zm4%23jC0DDHA.2456@server53...
> 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.
>
> I tried to exlucde the table that causing the problem only to find another
> table causing the same problem.
> This is only happening on one server (the one I'm trying to compare to).
>
> Everything seems to check out fine on the database side. We've been
> getting this error for 3 weeks now and are unable to compare the
> databases. Any thoughts and suggestions would be greatly appreciated.
>
>
We've covered the possibilities that SQL DMO needed to be re-installed,
checked the database with DBCC, and did some queries to sysobjects looking
for these table objectIDs with no success.
Does anyone out there in DBA Land have any suggestions as to why SQL DMO
is being so naughty?
Brian Donahue
Red Gate Support...
"Don" <don_nguyen@scantron.com> wrote in message
news:Zm4%23jC0DDHA.2456@server53...
> 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.
>
> I tried to exlucde the table that causing the problem only to find another
> table causing the same problem.
> This is only happening on one server (the one I'm trying to compare to).
>
> Everything seems to check out fine on the database side. We've been
> getting this error for 3 weeks now and are unable to compare the
> databases. Any thoughts and suggestions would be greatly appreciated.
>
>
This discussion has been closed.
