Another alternative would be to use SSIS to import and validate your files prior to loading them in your database.

In addition to what everyone else has said, I would also tighten up your use of NULLs. Setting your columns up as NOT NULL by default is a good...

Yes. Combining string values with the '+' operator results in a NULL any time one of the values contain a NULL. This is expected behavior. Since NULL...

declare @test-2 TABLE (

ID int,

Code int,

CodeType char

)

INSERT INTO @test-2

SELECT 1, 10, 'A'

UNION

SELECT 1, 20, 'B'

UNION

SELECT 2, 15, 'A'

UNION

SELECT 2, 25, 'B'

UNION

SELECT 3, 35, 'A'

UNION

SELECT 3, 45, 'B'

SELECT * FROM @test-2

SELECT...

Where are you trying to execute the step from? What Adrian showed you is from BIDS.

So back to the question at hand, how to duplicate your SP logic within SSIS.

This on is pretty simple. You'll need a data flow with a flat file source...

My professional opinion would be that you're time would be better spent mastering non-cursor solutions and any other effort is wasting your time. Why spend so much time working...

I can't help but comment on the other few threads that you've started regarding advice on using cursors. Specifically, you asked in one thread about the use of nested...

What do you mean...

Did you try it?

DECLARE @var int

IF @Var IS NULL

SELECT 'It Works'

ELSE

SELECT 'Nope'

OK, so back to the question of why? What is the purpose of doing this, are you using this data elsewhere?

We're getting close by the way.....

I'm glad I'm not alone! 🙂

The second INSERT statement in your example shows Table1 being outer joined back to itself on it's key column. An outer self-join on the key column with the IS...

What is the deal with table1? Is this a temp table, table variable? What are you trying to accomplish with it?

If you are staging the data in a table and then using a stored procedure to 'link' those rows to related data and insert them into your destination table, then...