Good question. I would not expect this to happen. Are...

It looks like you've added to it. You don't need to VALUES clause. You are INSERTing the result set produced by the SELECT statement.

Also, you have...

Right, but if you will be using the WBS1 column to tell the Sp which row to copy over to your Projects_AssociatedContracts table, you only need one input parameter and...

If the WBS1 value uniquely identifies which row you want to copy to your destination table, your SP would look more like this:

CREATE PROCEDURE dbo.insert_AssociatedContracts

@WBS1 varchar(30)

AS

INSERT INTO [dbo].[Projects_AssociatedContracts] (

[WBS1],

[WBS2],

[WBS3],

[custProjectName],

[custProjectManager],

[custStartDate],

[custEndDate],

[custJobValue]

)

SELECT PR.WBS1,...

Just to clarify, I was not saying that you needed to use them, I was just raising the question as to whether they should be used or not. Using...

No problem, glad to help.

The input parameters are the values declared in your CREATE PROCEDURE statement beginning with @.

CREATE PROCEDURE dbo.insert_AssociatedContracts

@WBS1 varchar(30)

@WBS2 varchar(7)

@WBS3 varchar (7)

@Name varchar (40)

@ProjectMgr varchar (20)

@StartDate datetime

@EndDate datetime

@Firmcost decimal(19,4)

So...

This is still a simple LEFT OUTER JOIN, you just need to change the JOIN criteria to include the whole primary key.

SELECT a.*

FROM @tableA a

LEFT JOIN @tableB b

ON a.dealerid =...

No problem.

How about those extra input parameters on your stored procedure, are you planning on using them? If not, you can get rid of them as it...

Huh, sounds wierd. You should be able to use the data conversion transformation for this. I'm not saying your wrong and I believe you are getting erros, I'm...

My post was not the complete stored procecure. You'll want to take that code and put it in your CREATE PROCEDURE statement in place of what you have between...

If you are just trying to insert a row if it does not exist, why not use a lookup transformation? If your row has a unique key available, this...

You could use an integer column with the IDENTITY set on it and have it begin at 1000. Then create a computed column that takes the value 'P' and...

Yes, a loop or cursor will allow you to get one row at a time, but there are very few instances where this is needed. The vast majority of...

No, in fact this SP should not even run. If you create and run this SP, do you get errors? You should. This should be closer to...