Your screen shot does not show the right hand side of the properties box ...

I suggest that you scope the variables at the package level to ensure that they are persisted between tasks.

Your expression will contain variable names, not ?s.

You should be able to do this just fine by using an SSIS Expression as the SQL for your Execute SQL task.

Not that I know of - maybe someone else will have some ideas.

Visual Studio 2002 ???

You need SQL Server Enterprise Edition to use fuzzy lookup.

jpSQLDude (6/15/2011)

---

On a Dev server in SQL 2008 R2 I created a complex SSIS package. But we only have SQL 2005 in production, and I can't run this package in...

Or run an Execute SQL 'UPDATE' at the end of the import.

You may also like to check the LOOKUP transformation.

Check out Row_Number() function in BOL - it may give you what you need, with a bit of tweaking to get formatting and order how you want:

Select 10 * ROW_NUMBER()...

Use a connection for the log file and use an external config file or SQL Agent job property to override the connection properties to match whatever environment the package is...

Looks like it should work OK - what happens?

Try a couple of minor refinements:

WITH CTE AS (SELECT EmpID, TimeDuration

...

Sorry - bit pushed for time hence brief replies.

I meant build your subquery, including the UNION, and then apply the CASE on that.

;with cte as

(select f1

from t1

union

select

f2 from t2)

select case...

'No luck' doesn't help diagnostics much.

You never mentioned that you were using a UNION - you need to do the union first as a subquery and then build your case/sum...

SELECT

CASE WHEN f1 > 2400 THEN 2400

ELSE...

Why have you posted this script?

Something like this?

SELECT 'Plo_' + Vendor + '_' + Shipto + '_' + CONVERT(CHAR(5),GETDATE(),108),

*

FROM dbo.Product p

WHERE Weeks =...