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!
- This topic was modified 7 months, 1 week ago by Grinja. Reason: grammar :(