I work in a corporate environment where the creation of linked servers is absolutely prohibited. I asked the database administrator, and the only answer I ever received was "This is a policy." Therefore, I have to write and use SSIS packages to move data between databases when the need arises.
Can someone tell me what reasons could be behind creating such a policy? It seems to me unjustified.
The theory goes that if one server is hacked, any linked server will also be automatically compromised.
, , , . , , , .
, , , , , , , db . , db, db, , , .
, , .
Simple. - , " " . ( ) ( A B).
, , , . .
, . , .
. - . , :
, - .
"" - -, , ; . , , DBA . , . , , , .
. , SOA - .
P.S. : SOA , , , SOA fantasy kinda : -)
, .
:
" ",
" ", sys.server_principals, , NT: ( , )
" self" ( " " ), "domain\bob" . , SPN, AD.
OPENDATASOURCE, , adhoc . .
, , . , .
, FWIW.
Source: https://habr.com/ru/post/1710163/More articles:using apache mod_rewrite to parse SEO urls - phpMVVM template for a paint-like WPF application? - wpfWhat is a fishbone chart? - project-managementRails application.html.erb? - ruby-on-railsCleaning resources when WCF service is suddenly disconnected Sessionful - web-servicesXsd-based code generator for creating xml? - c ++Bad graphics programming graphics? - javaInternet Explorer and client certificate in IFRAME - c #Is there a library that can convert raster vector conversion for iPhone? - vectorBuild build in the cloud - cloudAll Articles