April 8, 2019 at 11:57 am
Hello,
I have a scenario that requires the import of flat files from a Network File Share to a SQL server 2016 DB.
There is an automated process that uses the BULK Insert functionality to load the files into tables based on some configuration tables.
Recently this has been raised as a security exception as using Bulk Insert over a network is not secured or encrypted.
Looking for recommendations on best practice to ensure the network traffic between the NFS and the SQL server using BULK Insert is 'secured'.
All feedback is welcome!
Cheers,
G
April 8, 2019 at 2:58 pm
For encryption, if the file is unencrypted, then you are talking about encrypting the network traffic between the servers hosting SQL Server and the NFS resource, right? In which case that is something to handle that the OS and/or network layer, and does not involve SQL Server.
As for the issue of BULK INSERT not being "secure", can you please clarify what the means? What is the specific concern here?
Take care, Solomon..
SQL# — https://SQLsharp.com/ ( SQLCLR library ofover 340 Functions and Procedures)
Sql Quantum Lift — https://SqlQuantumLift.com/ ( company )
Sql Quantum Leap — https://SqlQuantumLeap.com/ ( blog )
Info sites — Collations • Module Signing • SQLCLR
April 9, 2019 at 8:43 am
Hi Solomon,
Thank you for the response.
The concern is specifically that the data will be intercepted in transit between the SQL server and NFS whilst using a BULK INSERT.
Cheers,
G
April 9, 2019 at 2:19 pm
Use IPSec at the network layer (or VPN tunneling).
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply