Table Definition:
CREATE TABLE [dbo].[cider_detail](
[trsource] [char](1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[sourceid] [int] NOT NULL,
[subscriberid] [smallint] NOT NULL,
[logon] [varchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[clientnum] [varchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[accountnum] [varchar](10) COLLATE SQL_Latin1_General_CP1_CI_AS NULL,
[accountid] [int] NULL,
[datetime] [datetime] NULL,
[Date] [datetime] NULL,
[Time] [datetime] NULL,
...and a bunch more (27 fields total)
) ON [psCider]([trsource])
Indices:
CREATE NONCLUSTERED INDEX [IX_cider_detail_sourceid] ON [dbo].[cider_detail]
(
[trsource] ASC,
[sourceid] ASC
)WITH (PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF) ON [psCider]([trsource])
CREATE CLUSTERED INDEX [ix-clust_cider_detail_sub_date] ON [dbo].[cider_detail]
(
[subscriberid] ASC,
[Date] ASC,
[Time] ASC
)WITH (PAD_INDEX = OFF, SORT_IN_TEMPDB = OFF, DROP_EXISTING = OFF, IGNORE_DUP_KEY = OFF, ONLINE = OFF) ON [psCider]([trsource])
(of course, on the 2000 machine, they're on a filegroup, rather than a partition scheme)
WHERE clause:
trsource='f' and sourceid between
49428637 and 50087444
trsource/sourceid form a unique key for this group of records (though it is not guaranteed unique for all values of trsource)
That's all I can think of now that might be relevant; please feel free to request any other specific info. / comments
- Community
- SQL Data Compare Previous Versions
- Result is showing differences when keys match exactly
Table Definition:
CREATE TABLE [dbo].[cider_detail](
[trsource] [char](1) COLLATE SQL_Latin1_General_CP1_CI_AS NOT NULL,
[sourceid] [int	...
0 votes
