Posts

Showing posts from March, 2017

Powershell: Working In The Pipeline

Image
Hello again! To start off today, I'd first like to apologize to any actual followers I might have for the delay since my last post. In addition to still getting used to blogging, as we all, the world can get pretty chaotic and busy. Luckily,  things have finally settled down and now I can get back into this thing. I've been looking forward to this post for some time now. With having the chance to break in my new Dev Environment during my last post, I'm excited to put it to good use. My plan for this approach is to start with pipeline Basics (Overview, basic usae) followed by some more advanced concepts and concluding with a script related to the commands used in the examples. Pipeline Basics Anyone who uses Powershell is likely aware of piping and/or using the pipeline. For those unfamiliar, Powershell functionality allows a user to pipe objects between or after commands enabling them to be interacted with. For example, let's say you want to run a command to check th...

Powershell: Getting Familiar With SQL Querying (Take Three)

Image
Mistakes were made.........again Hello again! In case you haven't already figured it out, I really took a rather foolish approach to blogging, the correct motives and objectives are there but the execution was shit. Because of this, I've made some changes to ensure that I'm taking a professional approach to my blog. The keyword here is professional . One thing that I've constantly been struggling with has been distancing my job related work from my blog topics and content. The whole point of this blog is not for discussing the projects I'm working on at work but rather the concepts that I'm learning while doing so. As a result, I've basically been writing a variation of a given script or function that I was working on all from memory. The reason for this is because the only way that I can test my newly learned concepts is at work. I think now is as good of a time as any to change that. Construction in progress To mitigate this problem, the solution was...