|
Forgive me, this is probably pretty basic stuff, but my experience with PS mostly boils down to "someone made this script to grab a bunch of database tables and throw them in a series of CSV files" which has served me well under the conditions that I'm using a trusted connection and not directly supplying credentials to the database server (ex loading a .bak into my local instance of SSMS and spitting out all 700 tables into CSV files). In working on something I came across a bit of SQL script that was generating PS commands and...they included plaintext storage of the username and password of the user who was going to run the SQL and PS code because for whatever reason, these servers aren't using trusted auth. code:
I've messed around a bit with what I can find through google searches, and come up with an almost ideal solution: code:
code:
I'll admit I might be suffering from google exhaustion and this may be an incredibly easy thing to figure out for you all but...I'm at my wit's end!
|
# ¿ Apr 21, 2023 19:28 |
|
|
# ¿ May 14, 2024 21:21 |
|
Our product version 7 databases use Windows authentication. Our product version 8 databases use credential authentication. Thanks for the tips!
|
# ¿ Apr 22, 2023 12:34 |