A Fine Slice Of SQL Server
When you check the Change log for Power BI Report Server, Version: 1.20.8910.25479 (build 15.0.1115.165), Released: May 28, 2024 release notes mentioned about the security change made during this update to add the environment variable and system variable on the Power BI Report Server machine.
Read on to learn more about this and what it takes to correct the issue.
Comments closedTom Collins breaks the bad news:
Question: Is it possible to restore a higher version of SQL Server to a lower version though a .bak file?
Answer: SQL Server doesn’t support restores from a higher version to a lower version using .bak backup & restore method.
Click through for a demonstration of fact.
Comments closedChad Callihan kicks a hornets’ nest:
Migrating databases to new servers and configuring them for availability groups can be a complex process. It can be more complex depending on what type of sneaky features are in use by the databases being migrated. I encountered an interesting issue migrating a database that had been setup to use FILESTREAM and wanted to show the steps I took to identify and resolve it.
Read on for the issue and what happened. It was a small thing overall, but the kind of small thing that can eat up the better part of a day if you’re not aware of it.
Comments closedKunal Rathi troubleshoots an issue:
While deploying a DACPAC project to Azure SQL database using Azure DevOps, you may come across ‘A project which specifies SQL Server 2022 as the target platform cannot be published to Azure SQL Database v12.’ error. In this article, we will see how to fix this issue.
There are plenty of errors in Microsoft products that make little to no sense. This is, by contrast, a rather straightforward one, and Kunal shows how to resolve it.
Comments closedGilbert Quevauvilliers fixes an issue:
How to stop/fix Mirroring to a database in Microsoft Fabric
I recently had a challenge where the mirroring in Fabric stopped working because there was no activity.
For me to start this again when I tried to connect to a table it said the database was already being used to mirror as shown below.
Read on for a quick fix that Gilbert found.
Comments closedSteve Jones runs into an issue:
This was an interesting error, and I was able to duplicate it, so I decided to write a post on how to find the problem and fix it. The error after running DBCC CLONEDATABASE is:
NO_STATISTICS and NO_QUERYSTORE options turned ON as part of VERIFY_CLONE. Database cloning for 'atest' has started with target as 'aSmallTest'. Msg 2601, Level 14, State 1, Line 11 Cannot insert duplicate key row in object 'sys.sysschobjs' with unique index 'clst'. The duplicate key value is (885578193).The final key value (885578193) for you might be different, but the error is the same.
Read on to learn more about the issue, as well as how Steve was able to fix the problem.
Comments closedDavid Fowler turns it off then back on again, like a true IT professional:
I recently received a complaint that Query Store for a particular database was turned off, which was strange as that particular database has seen quite a few performance issues and I know that I’d ensured Query Store was enabled in the past.
No problem, I flicked the switch and Query Store was enabled again.
Half an hour or so later and I’m being told that Query Store is again disabled. What’s going on?
Read on to learn what to do if you get stuck with this problem.
Comments closedAndy Brownsword troubleshoots a problem:
I recently ran into an issue when trying to call a function from an ADF pipeline. The function returned a generic Internal Server Error with no details exposed. Here we’ll look at how to dig into the logs to identify the true cause of the failure.
In this instance the function was performing PGP encryption but this could apply to any function. Let’s start with the problem.
Click through for the very generic error message and how you can get the real details.
Comments closedChris Webb continues a series:
Continuing my series on Power BI memory errors (see part 1, part 2 and part 3), in this post I’ll look at the query memory limit which controls the amount of memory that an individual query can consume. This is a subject which I’ve talked about in a few blog posts in the past: hitting this limit is one of the reasons you’ll see the “This visual has exceeded the available resources” error which I blogged about here and and here. There’s also some official documentation here which is pretty good.
Read on to learn more about what settings you have available for it and a few more tips.
Comments closedTanayankar Chakraborty troubleshoots a strange issue:
Issue
An issue was brought to our attention recently where an azure SQL DB was throwing TempDB related errors although the customer felt that the TempDB usage never came close to the value published in the official Microsoft document. Here’s the error the customer had complained about:
Error
Here is a more detailed error text :
The database ‘tempdb’ has reached its size quota. Partition or delete data, drop indexes, or consult the documentation for possible resolutions.’. Possible failure reasons: Problems with the query, ‘ResultSet’ property not set correctly, parameters not set correctly, or connection not established correctly.
This was an interesting problem and, admittedly, I didn’t predict the twist.
Comments closed