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 … Continue reading Temporarily enable TLS 1.0/1.1? – Be sure you check this keys
Starting on dbatools version 1.0.31 we introduced better coverage for commands that make use of PowerShell Remoting. Which commands? Commands like Get-DbaComputerCertificate, Get-DbaPrivilege, Get-DbaClientAlias, just to mention a few of them, make use of the internal function Invoke-Command2 which uses New-PSSession when we run it against a remote computer. "Why have you changed it?" Let … Continue reading More PowerShell Remoting coverage in dbatools
I don't know about your experience when it comes to SQL Server Agent jobs but often I receive requests to grant permission so that clients can handle their jobs in an autonomous way. Any problem with that? It depends 😄 If you're not familiarized with the difficulty this can bring, let me share with you … Continue reading Allow SQL Server Agent jobs management for non sysadmins
Dear reader, before continue please open a PowerShell console and run the following command: If you are doing this on the date of this blog post, you have just installed dbatools v1.0! After more than 200 commits, the work of more than 20 contributors and 20 days since the last published version, dbatools v1.0 is … Continue reading dbatools v1.0? It’s available – Check it out!
Few days ago I received a request to restore a dozen of tables because someone have deleted more data than it was supposed. I immediately thought about dbatools for the job! NOTE: I also thought about SSMS "Import/Export Data". And this is ok when someone says "it's to run just once, just now". When you … Continue reading “Ups…I have deleted some data. Can you put it back?” – dbatools for the rescue
Probably you had the need to script out some objects from a SQL Server instance/database and this is quite easy. You just need to right click on the object (well...not on every single one, try it with an Availability Group :-), no script option available) select "Script XXXX as" and you have it. But have … Continue reading Scripting SQL Server objects with dbatools – Beyond default options
Few days ago a client requested the configuration of MSDTC (Microsoft Distributed Transaction Coordinator). NOTE: If you want to know more about it here is a nice FAQ from Microsoft blogs - MSDTC Recommendations on SQL Failover Cluster? The client has 2 machines: one an application server and one a database server. Both run on … Continue reading Access is denied – Using DTCPing utility between two Windows Server 2016
One of the good things, when we have new clients, is that sometimes they have needs that you never heard before. This does not necessarily mean that they are complex. As a matter of fact, they can be really simple..now the question is..are they doable? 🙂 From my experience, this can happen mainly because one … Continue reading SSMS GUI not working? Try to use T-SQL!
This post is to answer the question: "You are used to seeing in the format of yyyy-MM-dd right?" that I have raised on my blog post Don’t cutoff yourself with dates in T-SQL – Did you know…. As you could see from that blog post, my screen shots were from VSCode and in this case … Continue reading SQL Server Operations Studio and VSCode: The wrong default datetimeoffset format
This month’s T-SQL Tuesday is brought by Steve Jones (b | t) and he wants to know if triggers causes headaches or happiness to us. This is the 106nd edition of TSQL2sDay - an Adam Machanic (b | t) brainchild. Triggers are those kind of database objects that sometimes are the best bet but … Continue reading Triggers: The hidden logic that will strike back – TSQL Tuesday #106