Monitor SQL Server Disk Space Using PowerShell

Monitor SQL Server Disk Space Using PowerShell by Richard Vantrease 

http://www.mssqltips.com/sqlservertip/3109/monitor-sql-server-disk-space-using-powershell/?utm_source=dailynewsletter&utm_medium=email&utm_content=headline&utm_campaign=20140113

Problem

I work in an environment where getting new software approved is often quite difficult. We have a disk space monitor in place, but it doesn't provide the type of monitoring my team was looking for. Monitoring disk space is critical for DBAs In addition, we use mount points, which is not supported by our existing disk space monitor.

Solution

My solution is PowerShell centric. Many of you may wonder why a DBA would use PowerShell. I tend to use the following guidelines to determine whether I will use PowerShell or TSQL to perform a task.

• TSQL - If the primary function of the task is set based (Select, Insert, Update, Delete), I use TSQL
• PowerShell - If the task I am trying to perform has a significant amount of flow control, or needs to access objects that are not SQL, I tend to use PowerShell

Fuzzy-String Search: Find misspelled information with T-SQL by By Thomas Keller, 2014/01/10 (first published: 2012/09/18)

Fuzzy-String Search: Find misspelled information with T-SQL
by By Thomas Keller, 2014/01/10 (first published: 2012/09/18)

http://www.sqlservercentral.com/articles/Fuzzy+Match/92822/

Fuzzy-String Search: Find misspelled information with T-SQL

By Thomas Keller, 2014/01/10 (first published: 2012/09/18)

How many times has a user told you that they entered a contact into your CRM system, and now they cannot locate it by name? Then, after you help them locate it by some other means, it turns out that either the original entry or the search term was misspelled? Would you like your search to be able to suggest alternates when a key word is misspelled?

When "fuzzy" string matching is most helpful

Whether it's misheard, mistyped, poorly scanned, or copied and pasted from a bad source, misspelled information is a common irritant to the user. If a user can't find the record they're looking for quickly, they will probably enter it again. If it's your job to merge the duplicates, then it's to your advantage to provide your users with a "fuzzy" search option. It may take a few seconds longer, so don't make it your default search. Just give your users the option, and they will learn to try it when their first search doesn't find what they're looking for. If they start entering a new record anyway, you can also launch a background process right after the user fills in the key field(s), which can alert them to potential duplicates before they are ready to hit the save button.