Error Running in Job vs Debug Mode when a change is made to databaswe

Question

Error Running in Job vs Debug Mode when a change is made to databaswe

tracymcdon

Grasshopper

Points: 15
More actions
November 6, 2008 at 6:40 pm

#195767

I have created an SSIS package. The package runs successfully as a job.
When an object in the database that is used in the package is changed, the job will then error out.
However, this object that changed does not require a change in the package. Could be something as simple as code was commented out in a stored procedure.
If we then go into the package via debug mode and just run through the validation and then we run the job again (without doing anything to the job), the job will run successfully.
Any thoughts as to why this is happening?

Viewing 7 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Brandie Tarvin SSC Guru Points: 173108 More actions · Answer 1

We need a better description. What object are you talking about? A connection string? A table name? A column? A stored Proc?

Please clarify and we'll be able to help you better.

Thanks,

EDIT: Oh, and please include the error message. The more details the better.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

Kishore.P SSCrazy Eights Points: 8147 More actions · Answer 2

Kishore.P

SSCrazy Eights

Points: 8147

November 7, 2008 at 5:43 am

#895445

need complete information about your query.

tracymcdon Grasshopper Points: 15 More actions · Answer 3

Thanks for replying.

The change could be as simple as adding a comment to a stored procedure or recompiling a stored procedure. Obviously, if a column name changed and it was reference in the package, then it would fail. But things that are changing that should have no impact on the package, are in fact, impacting the package.

So, literally, when we do nothing else but open the package, revalidate it and then run it, it works.

Brandie Tarvin SSC Guru Points: 173108 More actions · Answer 4

What is the error you get when you make these changes?

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.

tracymcdon Grasshopper Points: 15 More actions · Answer 5

Well, that is a good question. We did not have logging turned on, so we're not seeing the true error message(s).

Brandie Tarvin SSC Guru Points: 173108 More actions · Answer 6

So you're running this from the server? Not from BIDS?

If so, then create a job with an Operating System Command line and insert the Command Line from the "Run Package" screen. Then have it output (and include step output) into a text file somewhere on the server. That will give you the error message.

Brandie Tarvin, MCITP Database AdministratorLiveJournal Blog: http://brandietarvin.livejournal.com/[/url]On LinkedIn!, Google+, and Twitter.Freelance Writer: ShadowrunLatchkeys: Nevermore, Latchkeys: The Bootleg War, and Latchkeys: Roscoes in the Night are now available on Nook and Kindle.