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.
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.
We have seen how we can export and save the results to a folder and commit them to a GIT repository on my last blog post Backup your SQL instances configurations to GIT with dbatools – Part 1. At the end of that post, I have mentioned that I would write about how we can lower down the execution times of our script by leveraging on parallelism. Going parallel When we need to manage dozens of servers/instances, even with automated scripts sometimes we would like that our script finishes faster.
Today I want to share how I’m keeping a copy of instances’ configurations using dbatools. Chrissy LeMaire (B | T) wrote about it before on the Simplifying disaster recovery with dbatools blog post. In this post, I will add one step and save the output on a GIT repository. Pre-requirements You need a GIT repository GIT tools installed on the server where you are running the script so you can commit your changes dbatools A list or a place to get all instances that you want to run the export Preparation Git repository Clone your repository to a location where dbatools can write to.
Continuing to share tips and tricks using dbatools like the Refresh databases that belongs to availability group using dbatools posted a few days ago, today I will share a way to export the permissions of a login/user at instance/database level and apply them to a new login/user. The typical request Client: “We have a new colleague, can you please grant them the exact same permissions I have?!” A quick note/suggestion that may help minimize your work: If we are talking about a Windows Login, please suggest the use of AD groups to help you (so that you don’t need to do this process) and also them (they don’t need to make this request).
- OLDER POSTS
- page 1 of 2