Access violation at address 0000000000000000 in module 'AdvancedETLPro.exe'. Exe

Also, what is an update key?

I forgot to give you this table:
CREATE TABLE [dbo].[Tld](
[TLD] [varchar](10) NOT NULL,
[Block] [bit] NOT NULL,
[Type] [varchar](10) NULL,
[ForSale] [decimal](18, 0) NOT NULL,
[SalesHistory] [decimal](18, 0) NULL,
[Zones] [decimal](18, 0) NOT NULL,
[CreatedDate] [date] NOT NULL,
[Notes] [varchar](200) NULL,
CONSTRAINT [PK_Tld] PRIMARY KEY CLUSTERED
(
[TLD] ASC
)WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON, OPTIMIZE_FOR_SEQUENTIAL_KEY = OFF) ON [PRIMARY]
) ON [PRIMARY]
GO

ALTER TABLE [dbo].[Tld] ADD CONSTRAINT [DF_Tld_Block] DEFAULT ((1)) FOR [Block]
GO

ALTER TABLE [dbo].[Tld] ADD CONSTRAINT [DF_Tld_ForSale] DEFAULT ((0)) FOR [ForSale]
GO

ALTER TABLE [dbo].[Tld] ADD CONSTRAINT [DF_Tld_Zones] DEFAULT ((0)) FOR [Zones]
GO

ALTER TABLE [dbo].[Tld] ADD CONSTRAINT [DF_Tld_CreatedDate] DEFAULT (getdate()) FOR [CreatedDate]

Here is sample data for TLD.

On the transformation I rebuilt, I had the update key. Interestingly enough, I did not get any errors or validation around that.

Everything seems to work great on smaller datasets. When working with 159 million rows is when my select statement and ETL has issues. Looking at the select statement, I think I can rework it a bit to get better use of indexing.


Dean

If the record set is smaller, everything seems to work.