One table not listed in Choose Tables
Brian Donahue
Posts: 6,590 Bronze 1
Hi DRI,
This is a fairly common problem with Data Compare. If you check some of
the other threads, you'll see some reasons for the table not being visible
that have to do with a software bug. The bugs are fixed in version 3.01, but
there is still one outstanding issue: If the table has a Primary Key index
with a different name in one database than the other, the table will not be
available. Some system-generated index names can be different, so that's
something to check. It's fairly easy to fix, though, because all you'd have
to do is rename the index through Enterprise Manager.
I hope this helps.
Brian Donahue
Red Gate Technical Support
"DRI" <nospam.support@DRIDefault.com.nospam.nospam> wrote in message
news:ZHf%23ABkbDHA.2560@server53...
> Hi,
>
> Running SQL data compare for the first time so that I can generate an SQL
> data script for the information in one table.
>
> I start the SQL data compare and choose the two servers (using Windows
> Auth). After clicking next the Choose Tables dialog is presented and the
> table I want, called "CODES", is not listed. This is the table who's data
I
> want to read and create a script from. To troubleshoot I have tried the
> following:
> -- Use SQL Auth instead of Windows Auth
> -- Swap which server is 1 and which server is 2
> -- Verify the table is listed in the DB's via SQL 2000 Enterprise Manager
> -- Verify table has a unique key field
>
> Some important notes for this table:
> -- There is unique key that is auto incremented by the server. It is
called
> "UNIQ_ID" and it is an INT beginning at 1 and incrementing by 1
> -- The table is a driver table used for the database system. Most entries
> are located by an index on two fields (Field1+Field2 = [value])
> -- The table is fairly static and not updated often in the system
(compared
> to other tables)
> -- Tests in Query Analyzer indicate CODES not a reserved word
> -- Table is empty in one DB but not the other (although this is the case
for
> most of the tables including the ones that did show in the listing).
>
> Any help would be great. If this would work I'd buy a copy.
>
>
This is a fairly common problem with Data Compare. If you check some of
the other threads, you'll see some reasons for the table not being visible
that have to do with a software bug. The bugs are fixed in version 3.01, but
there is still one outstanding issue: If the table has a Primary Key index
with a different name in one database than the other, the table will not be
available. Some system-generated index names can be different, so that's
something to check. It's fairly easy to fix, though, because all you'd have
to do is rename the index through Enterprise Manager.
I hope this helps.
Brian Donahue
Red Gate Technical Support
"DRI" <nospam.support@DRIDefault.com.nospam.nospam> wrote in message
news:ZHf%23ABkbDHA.2560@server53...
> Hi,
>
> Running SQL data compare for the first time so that I can generate an SQL
> data script for the information in one table.
>
> I start the SQL data compare and choose the two servers (using Windows
> Auth). After clicking next the Choose Tables dialog is presented and the
> table I want, called "CODES", is not listed. This is the table who's data
I
> want to read and create a script from. To troubleshoot I have tried the
> following:
> -- Use SQL Auth instead of Windows Auth
> -- Swap which server is 1 and which server is 2
> -- Verify the table is listed in the DB's via SQL 2000 Enterprise Manager
> -- Verify table has a unique key field
>
> Some important notes for this table:
> -- There is unique key that is auto incremented by the server. It is
called
> "UNIQ_ID" and it is an INT beginning at 1 and incrementing by 1
> -- The table is a driver table used for the database system. Most entries
> are located by an index on two fields (Field1+Field2 = [value])
> -- The table is fairly static and not updated often in the system
(compared
> to other tables)
> -- Tests in Query Analyzer indicate CODES not a reserved word
> -- Table is empty in one DB but not the other (although this is the case
for
> most of the tables including the ones that did show in the listing).
>
> Any help would be great. If this would work I'd buy a copy.
>
>
This discussion has been closed.
