We have a production SQL 2005 cluster running SSIS, and we need to restart
SSIS. Is it safe to restart the SSIS service without affecting general
database operations and connectivity?
--

Mike

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Yes, it should be safe to restart ONLY the SSIS service from either SQL
Server Configuration Manager or the Services snap-in.

Obviously it will affect anything that might try to access it during the
down-time, like a SQL Agent job that tries to run a package, but for general
transactional database users, there should be no issues.

HTH
--
Todd C

[If this response was helpful, please indicate by clicking the appropriate
answer at the bottom]


"Mike Baker" wrote:

Thanks Todd.
--

Mike


"Todd C" wrote: