Ignore column order?
Johan Van Hoye
Posts: 12
Can I somehow indicate that I do not want to mark a different column order between two tables in two databases as a difference?
Thanks
Thanks
Cheers,
Johan
Johan
This discussion has been closed.
Comments
Could you double check that the option in the Project Configuration > More Options dialog called "Force column order" is disabled?
If you are still getting a difference is it possible for you to post the schema of the two tables concerned so that we can take a closer look at the problem?
Regards,
Jonathan
-Project Manager
-Red Gate Software Ltd
I'm seeing the same thing whether or not that option is checked.
Left:
CREATE TABLE [dbo].[t_trn_warranty]
(
[entity] [d_entity] NOT NULL,
[organisation_code] [d_organisation_code] NOT NULL,
[warranty_nr] [d_warranty_nr] NOT NULL,
[year] [d_year] NOT NULL,
[period] [d_period] NOT NULL,
[customer_nr] [d_customer_nr] NOT NULL,
[related_deal_id] [d_deal_id] NOT NULL,
[warranty_type] [d_warranty_type] NOT NULL,
[status] [d_status] NOT NULL,
[party_id] [d_party_id] NOT NULL,
[currency] [d_currency] NOT NULL,
[ccy_amount] [d_amount] NOT NULL,
[lcl_amount] [d_amount] NOT NULL,
[begin_date] [datetime] NOT NULL,
[expiry_date] [datetime] NULL,
[audit_date] [datetime] NOT NULL,
[audit_user] [sysname] NOT NULL
)
GO
right:
CREATE TABLE [dbo].[t_trn_warranty]
(
[entity] [d_entity] NOT NULL,
[organisation_code] [d_organisation_code] NOT NULL,
[warranty_nr] [d_warranty_nr] NOT NULL,
[start_validity_date] [datetime] NOT NULL DEFAULT ('19000101'),
[end_validity_date] [datetime] NOT NULL DEFAULT ('99991231'),
[related_deal_id] [d_deal_id] NOT NULL,
[customer_nr] [d_customer_nr] NOT NULL,
[book_code] [d_book_code] NOT NULL,
[year] [d_year] NOT NULL,
[period] [d_period] NOT NULL,
[source_system] [d_source_system] NOT NULL,
[warranty_type] [d_warranty_type] NOT NULL,
[status] [d_status] NOT NULL,
[party_id] [d_party_id] NOT NULL,
[currency] [d_currency] NOT NULL,
[ccy_amount] [d_amount] NOT NULL,
[lcl_amount] [d_amount] NOT NULL,
[begin_date] [datetime] NOT NULL,
[expiry_date] [datetime] NULL,
[last_modified] [datetime] NOT NULL DEFAULT (getdate()),
[modified_by] [sysname] NOT NULL DEFAULT (suser_sname())
)
GO
the field "customer_nr" shows up as new/missing either way.
This is on a SQL2000 SP4 with collation Latin1_general_bin.
Johan
Whilst SQL Differences panel will still highlight the [customer_nr] column as a difference, it is the other differences in the table (the different constraints and column for example) that are causing its status to be Different rather than Identical.
I understand that this is confusing and frustrating as it leads to false positives when viewing the SQL Differences panel. I have raised this issue with the developer concerned and we will look into this for future releases.
Jonathan
-Project Manager
-Red Gate Software Ltd