How can we help you today? How can we help you today?

Problem comparing tables with clustered index

Hi,
I'm having troubles comparing tables with clustered index created on them, because in two different databases, the code for the constraint is different:

Here it's an example:

On database DB1:
CREATE TABLE [dbo].[ACT_CNA02]
(
[ID_ACT_CNA02] [int] NOT NULL IDENTITY(1, 1),
[FILLER] [varchar] (20) NULL,
[CONCEP_AS] [varchar] (30) NULL CONSTRAINT b]DF__ACT_CNA02__CONCE__2BB470E3[/b DEFAULT (''),
[COTIZ] [DECIMAL_TG] NULL,
[CTE] [bit] NULL,
[FECHA_AS] [datetime] NULL CONSTRAINT [DF__ACT_CNA02__FECHA__2CA8951C] DEFAULT ('1800/01/01'),
[FECHA_VAL] [datetime] NULL CONSTRAINT [DF__ACT_CNA02__FECHA__2D9CB955] DEFAULT ('1800/01/01'),
[MON_CTE] [bit] NULL,
[N_ASIENTO] [ENTEROXL_TG] NOT NULL,
[TIPO] [varchar] (1) NULL CONSTRAINT [DF__ACT_CNA02__TIPO__2E90DD8E] DEFAULT ('')
)

On database DB2:

CREATE TABLE [dbo].[ACT_CNA02]
(
[ID_ACT_CNA02] [int] NOT NULL IDENTITY(1, 1),
[FILLER] [varchar] (20) NULL,
[CONCEP_AS] [varchar] (30) NULL CONSTRAINT b]DF__ACT_CNA02__CONCE__3BFFE745[/b DEFAULT (''),
[COTIZ] [DECIMAL_TG] NULL CONSTRAINT [DF__ACT_CNA02__COTIZ__3CF40B7E] DEFAULT (0),
[CTE] [bit] NULL CONSTRAINT [DF__ACT_CNA02__CTE__3DE82FB7] DEFAULT (0),
[FECHA_AS] [datetime] NULL CONSTRAINT [DF__ACT_CNA02__FECHA__3EDC53F0] DEFAULT ('1800/01/01'),
[FECHA_VAL] [datetime] NULL CONSTRAINT [DF__ACT_CNA02__FECHA__3FD07829] DEFAULT ('1800/01/01'),
[MON_CTE] [bit] NULL CONSTRAINT [DF__ACT_CNA02__MON_C__40C49C62] DEFAULT (0),
[N_ASIENTO] [ENTEROXL_TG] NOT NULL CONSTRAINT [DF__ACT_CNA02__N_ASI__41B8C09B] DEFAULT (0),
[TIPO] [varchar] (1) NULL CONSTRAINT [DF__ACT_CNA02__TIPO__42ACE4D4] DEFAULT ('')
)

Is there any solution for this? I'd like to have an option to disable the comparison of clustered index.
gocampo
0

Add comment

Please sign in to leave a comment.