January 3, 2011 at 11:32 am
I have an SSIS package that is configured to use transactions. Unfortunately it is failing because it it is pulling some data from another SQL Server on the network. After a bit of research it appears that I need to enable network transaction support in the DTC service for all the involved servers. What are the security, performance, or other issues/considerations that I may run into if I do this?
January 6, 2011 at 4:59 am
as from windows 2003 you had to enable network msdtc for linked servers to work.
The security implications are as good or as bad as your implementation - make the rights tight and specific using stored procs and it should be fine- allow ad-hoc table queries at sysadmin level - well do i have to state the obvious. Performance is no better or worse than it ever was for linked servers - I've always attempted to only ever allow remote proc calls - ad-hoc table queries have the potential to go very badly wrong, but it's always been that way.
[font="Comic Sans MS"]The GrumpyOldDBA[/font]
www.grumpyolddba.co.uk
http://sqlblogcasts.com/blogs/grumpyolddba/
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply