A Fine Slice Of SQL Server
Edwin Sarmiento digs into a failure:
Since we have experienced a number of unplanned outages and failovers on our SQL Server Always On Availability Groups, we want to know the root cause to prevent them from happening in the future. How do we identify the root causes of unplanned Availability Group outages and failovers?
Read on to learn how to use the AGDiag tool to answer this question.
Comments closedVlad Drumea troubleshoots a problem:
In this blog post I cover a fix for a weird behavior that bcp has when trying to import files that contain Unix line endings.
Read on for a description of what Vlad was trying to do, the problems you can run into when using bcp, how to fix those problems, and a bonus on how DBAtools is pretty neat.
Comments closedKellyn Gorman runs into an issue:
When I tried to connect via SQLPlus as SYSDBA, I received an EXTPROC error. It pointed clearly to the listener.ora file, which I discovered a path listed still to ora23c for the extproc, corrected it, started the Listener, but to no avail- an ORA-12547 error, realizing I had a make file issue on the binaries for Oracle.
I contacted Geral Venzl, who was very gracious and after some quick research, he came back that his folks said everything was fine with the images, so I thanked him and dug into the issue deeper. I quickly discovered this problem could happen to others, so decided I better document here for anyone who does happen upon it.
Click through for the high-level explanation and a bit more detail on dangling images.
Comments closedJonathan Kehayias (via Paul Randal) advises caution:
Recently I received an email with a very vague description of a problem that went something along the lines of:
“After some issues with Windows patching and rolling back from snapshots, our cluster resources won’t come online. In the process of troubleshooting the issue and validating the fix, we rolled back a few times. We can’t find any details about the issue in the cluster logs, Windows event logs, or SQL Server error log to investigate further.”
Read on for more information about the immediate problem, the root cause, and the actual issue the customer ran into before compounding the problem.
Comments closedChris Webb continues a series on Power BI semantic model memory errors:
In the Power BI Service, Import mode models are stored offline and paged into memory only when they are needed – for example because someone runs a report that uses the model as its source. As discussed in my last post, though, there’s a limit on the amount of memory that a model can use which varies by the size and type of capacity you’re using using. There’s also an extra complication in that Import mode models are stored offline in a compressed format that means the Power BI Service doesn’t know exactly how much memory will be needed if the entire model needs to be held in memory. As a result there is an additional limit enforced on the size of the offline copy of Import mode models to ensure they don’t use too much memory when they are eventually paged in.
Read on to learn more about this setting and what it looks like if you trigger the error.
Comments closedDeborah Melkin continues a series on Power Apps:
As a developer, I have two things I have to do: 1. Check code into source control and 2. Make sure I can use that code to deploy to any and all environments repeatably and successfully. The question then becomes, how do you do this when the development environment is in a portal?
Read on for the answer, as well as a tricky situation you might run into along the way.
Comments closedVlad Drumea is a trusting fellow:
This post covers a few ways to fix the SSL certificate error 1416F086 returned by sqlcmd on Linux when connecting to SQL Server.
If you’re looking for ways to fix the Windows equivalent of this error when using dbatools, check out this blog post.
It’s interesting how much controversy we’re seeing around tools like sqlcmd and (especially) SQL Server Management Studio defaulting to mandatory encryption. Having signed and valid certificates is a critical part of validating that this SQL Server is actually the one you think it is, and no intermediary attacker has swapped the certificate out with a phony one that allows the attacker to spy on your interactions.
I can understand people who are just messing around with SQL Server locally to experience pain on this, but the sheer number of actual companies—including companies using Central Management Servers, which implies having multiple SQL Server instances—with garbage-tier self-signed certificates is discouragingly high.
By the way, I’m aiming none of my rant at Vlad or this post. It’s just top-of-mind and this was as good a vehicle for rant delivery as I could find.
Comments closedTeo Lachev shares some advice:
Alerting is an important monitoring task for any ETL process. Azure Data Factory can integrate with a generic Azure event framework (Azure Monitor) which makes it somewhat unintuitive for ETL monitoring. You can set up and change the alerts using the ADF Monitoring hub.
Read on for five pieces of advice, in particular, covering how to set up one of these alerts.
Comments closedAndy Brownsword forgets something at home:
Within SSIS you can make use of custom components which aren’t present out of the box. An example of some would be the Azure Feature Pack if you’re working with cloud resources.
These will let us use features not available natively. They can also provide a challenge down the line when we come to deploy changes to the project.
Here we’ll look at an example of this challenge, how to troubleshoot, and ultimately resolve the issue.
Read on for the scenario and fix.
Comments closedThom Andrews shares a bit of advice:
A problem I’ve seen raised on numerous occasions is users that are getting a non-descript error when they are doing some kind of DML/DDL operation, and they don’t know why they are getting the error, and what is causing it. That error is:
Msg 3609, Level 16, State 2, Line 1
The transaction ended in the trigger. The batch has been aborted.
Read on to learn more about good alternatives, remembering that you’re in the context of some other call when a trigger fires.
Comments closed