This article was initially posted on SQLServerCentral @ 2020-08-18. It was interesting some comments I read about it, mainly why people still use WITH ENCRYPTION when it’s simple to overcome this when we have the right permissions. SQL Server offers an option to encrypt the code of your modules when using the WITH ENCRYPTION syntax. This allows to hide/obfuscate the modules’ code and thus keep away from prying eyes. It’s often used to protect business rules since it allows you to protect some intellectual property.
Whether it’s in our personal lives or the professional one, we do have checklists for certain tasks. On the professional level, it can be purely technical like SQL Server installation, configuration or even uninstall, but they can also be not so technical like when a colleague join the team and someone needs to request permissions to access the company’s tools (such as ticketing/incidents/VPN/etc). What about when a colleague leaves the company?
This was initial posted on SQL Server Central articles. As one of dbatools’ first members, I’ve been using it for years and it’s really my goto tool. This task was no different! Today’s tip and trick using dbatools is about generating an Excel workbook that contains lists of SQL Server roles and its members. The Usefulness of these Reports These reports are especially useful when performing tech-refreshes (migrating from an old version to a newer one) and you want to do some housekeeping.
The idea of this blog post, like many others I write, is to document a workaround solution to my problem. Hopefully I can also help someone that may be looking for the solution for this problem and stumbles accidentally (or not) on my blog. Scenario I was helping a colleague automating the creation of emails using Microsoft Outlook using PowerShell. The following are configurable options (these will be the parameters of the script):
There are some actions that we know that will have to be repeated from time to time, but the surprise comes when it’s time to do so and the process that used to work does not work anymore. This is a short post to document a slight change that I had to do to achieve the same final result as the first time. Long story short A client needed to run a setup to install an application.