Hi Elliot.

Excellent. That was what I was looking for. This allows me to load the file only once. Not several times if I want to populate the Parent Tables first...

I'm probably missing something but would a merge join not just give me existing data? I would still have the issue to populate the parent data into the corresponding table...

Textfile looks like this:

"Filername","AggregateName","SizeAvailable","SizeTotal","SizeUsed","SizePercentageUsed"

"ch-sto101","aggrfc01","4781005754368","12833602928640","8052597174272","63"

"ch-sto101","aggrfc02","3251355275264","5133441171456","1882085896192","37"

"ch-sto101","aggrfc03","2363434860544","6673473544192","4310038683648","65"

"ch-sto101","aggrfc04","5104901455872","6673473544192","1568572088320","24"

"ch-sto101","aggrsa01","2988296765440","14374022676480","11385725911040","79"

"ch-sto101","aggrsa02","1429209382912","9582681784320","8153472401408","85"

Table Filer

FilerID PK, int, not null (identity column)

FilerName nvarchar(255)

LocationID int,null

TypeID int,null

Table Aggregate:

AggregateID PK, int, not null (identity column)

AggregateName nvarchar(255)

ParentID FK, int

So when a new filer is found...