Saving your requests


March 3, 2022 by Kenneth Fisher

The other day a friend of mine mentioned that they were questioned on one of the scripts they ran recently and they were in fact able to pull that script back up and show them. I was reminded of something I’ve thought about writing several times so it seemed like a good excuse.

An old manager of mine started his team saving all of our work in folders on a shared network space. A few months back I started doing this again, just in sub folder of my documents folder.

In each folder are the scripts that I ran for that request, or at least notes on what I’ve done, assuming a GUI or whatever. And, if the output isn’t too large then I add it too. You’ll also notice that I’ve got a brief description in the folder name for some of them as well.

Now, if a co-worker, auditor, the original requestor, or whoever, needs to see a copy of the code I ran I have it available. And it’s easy to find since it’s listed by request number. The brief description means that if I need some old code (for example a restore process I’m doing over and over again) I can pretty easily find it without having to look up the old request number.

I mentioned that when I first did this it was in a shared location and this had the additional benefit that if one of the DBAs needed to pick up a project in the middle (the original person is out sick, busy, whatever) then they at least have a starting point.

Yes, this does take up some space, but let’s face it, if all you are doing is storing scripts and small (< a couple of mb) outputs you can store a lot of requests before you’ve taken up any kind of significant space.

4 thoughts on “Saving your requests

  1. Hi Kenneth, long time… For this purpose we utilize source control – Team Foundation Services (TFS) product in our case, where we keep all DBA, Infrastructure, Development, RDLs, DLLs, PowerShell and ETL scripts with convenient version controls that keeps all change set history. Every team has its own folder in TFS and we place all code from different developers/DBAs/admins into one shared space. This product allows to save comments for each change (such as ticket no, description of the change, requestor and more). We are in process of converting it into Azure DevOps and implement automated QA and deployments.

    • That certainly works. And is definitely better for code changes etc. I’ll admit we weren’t using source control at the time. But I’m not sure source control is appropriate for everything. For example a simple data update script to change a row’s status. Or just pulling some data to be put in a spreadsheet.

  2. […] Kenneth Fisher shares a good idea: […]

  3. way0utwest says:

    +1 for version control. I think this is good, but drop in git. That way you can pull the repo to any machine, or anyone else can

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Enter your email address to follow this blog and receive notifications of new posts by email.

Join 3,755 other subscribers

Follow me on Twitter

ToadWorld Pro of the Month November 2013
%d bloggers like this: