April 12, 2017 at 5:08 am
Thanks for explaining
April 12, 2017 at 10:53 pm
A dbcc freesessioncache command should clear the plain text password from the logs.
April 13, 2017 at 8:22 am
badOedipus - Wednesday, April 12, 2017 10:53 PMA dbcc freesessioncache command should clear the plain text password from the logs.
That should clear the password from the session cache, but won't it still be in the transaction logs?
plus that command requires sysadmin permissions. Something you don't want to hand out sparingly.
Plus anybody who has access to look at what is running would be able to see the password in plain text while it ran would you not?
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
April 13, 2017 at 5:35 pm
Mapping of a drive and assigning appropriate permission is an OS admin task, it must be done in a different place by a different user.
SQL Server must just use the existing mapped drive or report an error if expected mapped drive cannot be found.
_____________
Code for TallyGenerator
Viewing 4 posts - 16 through 18 (of 18 total)
You must be logged in to reply to this topic. Login to reply