Today, while help @meltondba with his SQLPS question on the enumerating jobs history, @LaerteSQLDBA provided a oneliner to provide this result. There’s one concern, should we use SQLPS instead of SMO. For this answer I’m going to point out MSDN article regrading the future of SQLPS in upcoming SQL Server releases: http://msdn.microsoft.com/en-us/library/cc280450(v=SQL.110).aspx
This article states that “… This feature will be removed in a future version of Microsoft SQL Server. Avoid using this feature in new development work, and plan to modify applications that currently use this feature. Use the sqlps PowerShell module instead. For more information about the sqlps module, see Import the SQLPS Module. …”
So, during this exercise I found out that I can out with the same number of line for either SQLPS and SMO. Both giving me the same results.
Here’s some picture ilustrating basic code snippet of both SQLPS and SMO to get some SQL Server Jobs information:
This pictures shows, it look simple enough. So, if you’re building SQLPS scripts, you can easily start transitioning your code to SMO.