What are the challenges you face when working across database platforms? Take the survey
Options

Force Column Order

edited July 12, 2016 8:16AM in SQL Compare 11
Dear Sirs,

I am using the Force Column Order setting to have the fields on a new table forced to be created at the correct position but when I start a compare and look at the result the fields are put at the end of the table.

This is a sample from the Create Table in Microsoft SQL Server Management Studio

CREATE TABLE [dbo].[SALE](
[SALE_ID] [uniqueidentifier] NOT NULL,
....
[TICKET_PRINT_STATE] [int] NULL,
[VOUCHER_NUMBER] [nvarchar](15) NULL,
[ORGANISM_NUMBER] [nvarchar](15) NULL,
[SALE_BITS] [xml] NULL,
[SALE_CITS] [xml] NULL

This is what the SQL Compare puts in the difference view
-- Columns

CREATE TABLE [dbo].[SALE]
(
[SALE_ID] [uniqueidentifier] NOT NULL,
....
[TICKET_PRINT_STATE] [int] NULL,
[SALE_BITS] [xml] NULL,
[SALE_CITS] [xml] NULL,
[VOUCHER_NUMBER] [nvarchar] (15) NULL,
[ORGANISM_NUMBER] [nvarchar] (15) NULL
)

So it seems that the switch Force Column Order is not working as expected? What am I doing wrong?

Greetings Danny.

Comments

  • Options
    It seems that we have 2 databases live one with the fields in the correct order and one with the fields at the end.

    The one database with the fields where already added to the end was created with an upgrade script from SQL Compare but it was executed without this Force Column Order Checked.

    We compared from this newly created database table (where the fields were already at the end) but we did not notice it.

    So the flag is doing as expected any way.

    Greetings Danny.
Sign In or Register to comment.