You might investigate using the file watcher task - check this thread for more details:

http://www.sqlservercentral.com/Forums/Topic493253-148-1.aspx

Phil

Can you use a script task?

If so, you can put the filename into a variable and then process it.

There may be an easier way, but script will work for sure.

Phil

Agreed and done.

Phil

If you enjoyed answering this question, you can do it all over again here:

http://www.sqlservercentral.com/Forums/Topic634483-148-1.aspx

Phil

Is this a homework question from a college course, by any chance?

This thread looks too similar to be a coincidence:

http://www.sqlservercentral.com/Forums/Topic634303-148-1.aspx

Phil

Sounds like security to me too. Try running the jobs in VS, but while logged in as the SQL Agent service user.

Phil

I suggest that you bring all of the data into a SQL Server staging table and then run one or more 'clean-up' queries on the staging table to do the...

Noffer (1/7/2009)

---

---

So, I goggled the code and came up with the following page in the Microsoft Knowledgebase...

http://support.microsoft.com/kb/933835 Does this look like its the source of our problem? Or...

Where is the status field? Is it in a SQL Server table?

I understand your logic about importing:

1) Needs to be extracted from Oracle

2) Has been extracted from Oracle and is...

00 is NULL - whether that helps you at all is another matter 🙂

Phil

maria.protopapadaki (1/7/2009)

---

Phil,

Interesting, Task2 does not run when @Variable=="" is the expression (and the output param is indeed an empty string, so one would expect the task to run)

I guess this...

If you change the constraint to

@[User::MyVariable]==""

does it still run? That is, is the constraint being completely ignored?

I am not suggesting a scheduling problem. I am suggesting the possibility of a user-privileges problem. Maybe your script does something that you (or the user that you were logged...

Can you log in to your system interactively as the same user that runs the scheduled job (ie the SQL Server Agent user) and then try running the job again...

How can anyone help you when you ask a question like this? Please provide more...