Steve Jones - SSC Editor (7/28/2008)

---

Good explanation. OLEDB is newer and superceeds ODBC. You should aim to use OLEDB connections where possible. I believe there's an OLEDB provider that encapsulates...

Charmer (10/8/2012)

---

Phil Parkin (10/8/2012)

---

Charmer (10/8/2012)

---

Phil Parkin (10/8/2012)

---

Are you doing the imports in parallel or in series?

A no-code solution could utilise FOREACH containers - the container just does not execute if...

Four tables with different structures to one file?

I've downloaded and installed SSMS Boost. Some interesting features and some usability issues too (eg Script Object as CREATE/ALTER fails with 'No suitable objects found at cursor position' unless you...

Charmer (10/8/2012)

---

Phil Parkin (10/8/2012)

---

Are you doing the imports in parallel or in series?

A no-code solution could utilise FOREACH containers - the container just does not execute if the file is...

Are you doing the imports in parallel or in series?

A no-code solution could utilise FOREACH containers - the container just does not execute if the file is not there and...

mubarak.a (10/8/2012)

---

Hi,

I'm new in SQL Server, i want the working process of STUFF & ISNULL. How it works & how it concatenate the row level data into a single data?...

Is there a chance that you could post this in English?

Most people here communicate in English and I think you will find that you get a better response if...

+1

impossible to help with this without getting an idea of what the file looks like and what you need out of it.

Thanks to all who have responded with their ideas. I've been away for a couple of days & will be coding my solution this coming week.

Jeff, I have worked through...

CELKO (9/27/2012)

---

First, let's fix your DDL. There is no such thing a “type_id” in RDBMS; read ISO-11170 or any book on data modeling. Would you say “blood_type_id”? Of course not!...

Have a look here and see how you get on. It does something similar to what you require.

Hmm - it seems that I have had a go at helping someone solve this issue in the past - check here.

It would seem to be a problem specifically related...

Hardy21 (9/27/2012)

---

Yes Phil. It is...

Is the ResultSet property of the ExecuteSQL task set to SingleRow?

Have you mapped 'TableExists' to your package variable on the Result Set property page?