Do I need to restart computer to

Question

Do I need to restart computer to

sqlfriend

SSC Guru

Points: 52794
More actions
August 15, 2011 at 4:16 pm

#255519

We have a ssis package using enviroment variable for configuration file.
I found it was created wrong first. so I deleted it.
Now I recreated a new one, but my package still doesn't run in SQL server agent.
Do I need to reboot the computer for it to take effect?
This is a production server, it's so hard to do it in day time.
Thanks

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

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

Steve Jones - SSC Editor SSC Guru Points: 738803 More actions · Answer 1

You do not need to reboot to run a package.

IIRC, the package is scheduled by it's internal GUID, not name, so if you re-created it, you need to rebuild the job that runs it.

sqlfriend SSC Guru Points: 52794 More actions · Answer 2

I didn't recreate the job, I just changed the package configuration to point to the newly created enviroment variable.

So I don't think I need to recreate the job or schedule.

But I just want to know is it necessary to restart computer for enviroment varible to take effect, or just start sql server services, sql agent services?

Thanks

Steve Jones - SSC Editor SSC Guru Points: 738803 More actions · Answer 3

You shouldn't have to restart SQL Server.

An environment variable should be read when it's accessed. Depending on how you created it, it's possible that it needs a new logon to become visible. If your package runs under the SQL Server Agent service, you might need to restart that service to have it visible.

sqlfriend SSC Guru Points: 52794 More actions · Answer 4

Yes, I restart both services, the job seems run successfully.

Thanks

Steve Jones - SSC Editor SSC Guru Points: 738803 More actions · Answer 5

Thanks for the update. I believe for all OS versions, you need to log off and log on for new variables to appear. In your case, it would depend on how the job is being run (under which account).