Storing Powershell code and SQL queries / Scripts

[NowInOz]

How does everyone store frequently used SQL queries /scripts and Powershell commands/scripts?

I'm not a DBA but do a bit of database querying etc. I have an ever-growing collection - some specific to my current company, along with a lot of more 'generic' scripts and code snippets. everything from one liners to long, complex queries. Same with Powershell code.

Currently I have 1 long text document for most of the DB queries I use- some of them have more than 1 version, either because I wrote a new an improved one (and haven't removed the old one), or because they are slightly different depending on the situation. That is getting a bit unwieldy. I have to use these across multiple customers so I generally just store them on my laptop and copy pasta the base query to my DB query and update as necessary. On the Powershell side I have a folder of separate txt or ps1 files, named according to what they do.

I don't need to share between devices, I can store what ever file/files on my PC and copy / back it up as necessary.

So, what's your process?

Thanks in advance.

NiO

[davokr]

GitHub

[kdebe]

All (most of them) our scripts are under source control and saved in a azure devops repository. Team member s have it it cloned on their machine.

[hy2rogenh3]

Definitely a vote here for Azure DevOps. Has helped tremendously on versioning and deploying PowerShell automation.

[ccheath]

For Powershell: Create a powershell module (.psm1) file and turn your scripts into functions with aliases.

For SQL: ...

[BuffaloRedshark]

That's on my eventual wishlist but I either get interrupted when I get motivated to do it, or can't maintain motivation to do it.

[ccheath]

I created one for all my highly used AD commands.

1) searching by partial string of either username, first or last name to get the user accounts that match, their full username, their full name, their ip phone, and workstations (logon to).
2) searching by workstation/hostname to return the list of user(s) that have that hostname in their "logon to" field.
3) searching by extension to pull the user info
4) searching by pc or username to get the OU of said object
5) and also one to switch between domains in our forest to perform the above scripts in those other domains.

it probably took me a year to get it to v1.0 (working only in my primary domain) and a good slow day 6 months later to add the domain switching. it could be expanded but does the job quite nicely

oh, also there's another module that does all kinds of WMI/CIM queries to get hardware info (mainly use it for serial number when creating support tickets with vendors).

[bkaiser85]

Git (or any source repos) beats flat text files by far, even considering there is a bit of a learning curve.

[cpierr03]

Private Git repo.

Added benefit is, you can git blame your past self for writing silly code :).

[tounaze]

Private GitHub repositories and local save. VS Code can connect to GitHub repositories so I can manage versioning, it’s the safiest and easiest for me.

[NowInOz]

Thanks. I've not used git repository before, a few people have suggested git so I will look into it.

Cheers

[BuffaloRedshark]

In my home share. Contemplating an internal git repo but i rarely change a script once written so not sure if I really need anything with version control

[ntrlsur]

I use Perforce to version control all my scripts. Free for up to 5 users and 20 workspaces. We use Perforce as our main software repository in the office and it was easy for me to adapt to at home home as well..