<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SQL on PowerShell.org - Welcome Automaters!</title><link>https://powershell.org/tags/sql/</link><description>Recent content in SQL on PowerShell.org - Welcome Automaters!</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 27 Jul 2020 18:24:52 +0000</lastBuildDate><atom:link href="https://powershell.org/tags/sql/index.xml" rel="self" type="application/rss+xml"/><item><title>Creating a PowerShell Module to Improve Your Code</title><link>https://powershell.org/articles/2020-07-27-creating-a-powershell-module-to-improve-your-code/</link><pubDate>Mon, 27 Jul 2020 18:24:52 +0000</pubDate><guid>https://powershell.org/articles/2020-07-27-creating-a-powershell-module-to-improve-your-code/</guid><description>&lt;p&gt;Do you have PowerShell code that you reuse in your scripts over and over? Do you have server names hard coded in variables? Are you using a text file or CSV file to import server names? Do you find yourself only utilizing one server out of a cluster of servers to make your PowerShell commands? These are the questions I asked myself and the answer used to be YES. In this post, I will go over how you can store your infrastructure server information in a SQL database and call that data from a custom PowerShell module. By utilizing this method, you can expect the below benefits:&lt;/p&gt;</description></item></channel></rss>