The primary DTS security issue is related to the security context in which
DTS runs and what you have exposed to that security context. You have to
analyze what the pipe you have opened potentially exposes to the outside
world. This is much the same issue for any data movement.
Can anyone explain the security issues involved with using a DTS
package to transfer sensitive data (bank info is encrypted, but other
customer info is sensitive) from a SQL Server on our internal network
to a SQL Server on our DMZ?
Re: Scheduled DTS package fails even when SQLSERVERAGENT logs on as ow ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)...www.SQLDTS.com - The site for all your DTS needs. ... > Successful DTS package fails when scheduled as a SQL Agent job.... > between Agent and DTS security context as far as Access is concerned? ... (microsoft.public.sqlserver.dts)
Re: Scheduled DTS package fails even when SQLSERVERAGENT logs on as ow ... > And in what DB role on SQL Server is domain\user1? ... > www.SQLDTS.com - The site for all your DTS needs. ... >> Successful DTS package fails when scheduled as a SQL Agent job.... >> between Agent and DTS security context as far as Access is concerned? ... (microsoft.public.sqlserver.dts)
Re: DATA Export ... When you run DTS package manually it runs in your security context.... Check the security settings in scheduling program.... If I use the SQL planer,... (microsoft.public.sqlserver.dts)
Re: Scheduled DTS package fails even when SQLSERVERAGENT logs on as ow ... Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)...www.SQLDTS.com - The site for all your DTS needs. ... >> www.SQLDTS.com - The site for all your DTS needs.... >>> between Agent and DTS security context as far as Access is concerned? ... (microsoft.public.sqlserver.dts)
DTS Run ... I have a little problem with the security context of DTS. ... I have 2 DTS, the first DTS is started through an ASP page, No ... use the user context. ... (microsoft.public.sqlserver.dts)
