Are you referring to this type of table variable?

The older type of table variable is not in-memory. Nor is it good for holding large quantities of data.

Welsh Corgi (1/14/2016)

---

I execute the following Query:

INSERT INTO POSTAL (ID,Latitude, ID.Longitude, CityTownshipID, CountyRegionID,StateProvinceID,CountryID)

SELECT ZipCode, Latitude, Longitude,CityTownshipID , CountyRegionID, StateProvinceID, CountryID

FROM Postal_Codes_Import

WHERE NOT EXISTS (SELECT *

...

Welsh Corgi (1/14/2016)

---

Phil Parkin (1/14/2016)

---

The WHERE NOT EXISTS () construction often performs better than using a LEFT JOIN – I would recommend a test.

You should include table schemas in your...

The WHERE NOT EXISTS () construction often performs better than using a LEFT JOIN – I would recommend a test.

You should include table schemas in your code to avoid the...

Why would the Id be the same as the ZipCode?

Script Component Source is where I would start, yes ...

Grumpy DBA (1/14/2016)

---

Luis Cazares (1/14/2016)

---

Phil Parkin (1/14/2016)

---

Grumpy DBA (1/14/2016)

---

Another death, actor Alan Rickman (of Professor Snape and Die Hard fame) died at the age of 69 - oddly the same...

sqlnewbie17 (1/14/2016)

---

If my result set has a million rows wouldn't a case statement be very slow than a where clause.

Is there a better way of doing this.My environment is sqlserver...

Are you opening a VS solution which includes the package? Or attempting to open the dtsx directly?

Remove the where clause.

Add a column to your select

Iif (Cola >Colb, 'true','false')

Grumpy DBA (1/14/2016)

---

Another death, actor Alan Rickman (of Professor Snape and Die Hard fame) died at the age of 69 - oddly the same age as David Bowie. This...

I disagree. Well, it may be what you are looking for, but it does not match your original requirement.

In order...

PearlJammer1 (1/14/2016)

---

Its a good question. I have just asked the same question regarding the data type changing at any point and I am waiting for an answer. This is a...

I would say yes. But as this is a job, presumably it was working before? Or has the proc definition changed recently?

Did you try putting your DISTINCT on the nested SELECT?