John Rowan (5/1/2009)
I have a package that does the exact same thing. Here's how it is set up:1. Package does some import stuff.
2. Execute SQL Task checks table row count:
- Result Set - Single Row
- Source - SELECT COUNT(*) as ProductionCount FROM Table
- Result Set tab
- Result Name - 0
- Variable name - User::ProductionCount
3. Precedence constraint w/ expression checking @User::ProductionCount > 0
Pretty simple in theory, but it seems like I always have to jump through a few hoops to get an Execute SQL task to populate the variable. In this case, I found that I needed to have the COUNT(*) alias match the variable name in SSIS. Wierd, but it works.
Are you using an Execute SQL task to populate your variable?
Yes, I am using an execute SQL task to populate the variable. I noticed you set the result name to 0. I changed my result set name to 0 as well, but this still did not fix the issue.
This should in theory be very easy... thanks for your help thus far!
_______________________________
[font="Tahoma"]Jody Claggett
SQL Server Reporting Analyst[/font][/size]