The postings on this site are my own and do not represent my Employer's positions, advice or strategies.

LifeAsBob - Blog

 

Home

No Ads ever, except search!
Tuesday, May 20, 2025 Login
Public

rbio_await_response4/11/2025 5:34:48 AM
Began seeing a new wait time for Azure SQL Server on hyperscale tier, rbio_await_response.

It is not affecting performance, but does show up as a wait time with no sql statement associated with it.

Response from Microsoft is that this was the result of a recent patch and they are researching.

Logins coming from user {machine}\\{windows fabric user} or NTAUTHORITY\SYSTEM and they are related to some of our internal tasks like Backup or running other background tasks. You may see the same logins in sp_who2 running system threads as well. There’s no negative performance on the db because of this wait type and the queries coming from System user and the program name Fabric:/Worker.Vldb.Compute/facb87701e95. In fact, Fabric:/Worker.Vldb.Compute/facb87701e95 is basically the HS behind the covers.

We are working internally and exploring available options to correct this behavior.


A copilot generated image, including odd spelling:


4/11/2025 5:34:48 AM | Web_Blog
Stop using locking hints in Azure SQL1/17/2025 6:03:08 AM

Once habits are hard to stop.

Teams begin using with (nolock), holdlock and they just keep using.

Mostly leftover if you can believe from sql 2000 based DBAs, yep that long.

Developers don't understand locking, let alone new enhancements to it in azure sql or sql 2025.

There may be a reason to use a lock hint, but usually when I ask, there is no reason given other than "this is the way we have always done it."


Even before the new locking optimizations teams were advocating to STOP with the locking hints.

RCSI configuration is ON by default

SQL Server has many isolation levels to control the integrity of the data.

However, in read-heavy applications, many developers have the terrible habit of using NOLOCK on all statements to avoid the contention of creating lock records on the server. The developers ignore the risk of incorrect results.

Over the years, Microsoft created a solution for SQL Server: Two new isolation levels, RCSI (Read Committed Snapshot Isolation) and Snapshot Isolation; both also called optimistic isolation levels.

RCSI is considered a special isolation level. It’s different from the other isolation levels because RCSI is configured as a database property. There is no need to change the code. Every transaction that arrives on the server using Read Committed isolation (the default) is converted to Snapshot Isolation. I’m using quotes here because it’s not exactly Snapshot Isolation. RCSI has some differences from Snapshot Isolation, and that’s why they are considered two different isolation levels.

The point is: Azure SQL uses RCSI by default. This is a big change for all existing applications. Any use of NOLOCK that you have in existing applications becomes useless and a problem for the application because it brings the usual issues of NOLOCK with no benefit, since the use of RCSI replaces all the possible benefits of NOLOCK.

You can check this default on Azure SQL running the following query:

An image showing the results of checking is_read_committed_snapshot_on

Migrating applications to Azure SQL and using RCSI are great opportunities to eliminate all NOLOCKs still found in your SQL code.



1/17/2025 6:03:08 AM | Web_Blog
Crowdstrike BSOD reboots corrupts PowerBI Config files7/24/2024 6:24:50 AM
Recent crowdstrike issue causes BSOD.

Teams began repeatedly rebooting servers to try and correct.

Eventually the issue with crowdstrike is resolved, but now power bi report server service will not start.

On review the web.config and office.config and several other .config files were corrupt, restored from other server / backup.

Service still had issues, so had to run repair service.

Fun times...
7/24/2024 6:24:50 AM | Web_Blog
AJ Graduation 20245/30/2024 1:14:57 PM
AJ Graduation 2024

All 3 boys have completed the work...



5/30/2024 1:14:57 PM | Web_Blog
No posts for 1 year5/30/2024 1:03:36 PM
Goal accomplished, no posts for 1 year !
5/30/2024 1:03:36 PM | Web_Blog
Visual Studio IIS Debug web project5/29/2023 12:44:58 PM
Sometimes the debugger won't launch.

Make sure visual studio started as an admin

Sometimes permissions are lost.
elevated command prompt

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Aspnet_regiis.exe -ga domain\user

C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files

5/29/2023 12:44:58 PM | Web_Blog
IIS NT Authentication Stopped working2/19/2023 6:39:09 AM

Just an internally hosted web site, for use by members of my group on our domain.  Been working for years, suddenly today it begins prompting for credentials and/or wouldn't load.  Of course no changes, but there are always changes we can't control when you work in a big organization, group policy changes and patching being the biggest.

This same server, also hosts SSRS and it was authenticating fine with windows / nt authentication, so we knew it wasn't a problem of the server.

Ultimate credit goes to Ben Reese for helping solve this ! 

Ben sent me this so I could put it here as a place holder so we can remember the fix.

Followed these steps:

https://success.outsystems.com/Support/Troubleshooting/Application_runtime/Issues_logging_in_with_Integrated_Authentication_in_Internet_Explorer_or_Edge

 The solution for this is to disable the NEGOTIATE protocol in IIS, so that NTLM is always use. In sporadic situations, or to confirm the problem, you may want to disable NEGOTIATE in the client workstation.

  1. Access IIS Manager;
  2. Expand <server> Sites Default Web Site;
  3. In the IIS group, choose Authentication;
  4. Click Windows Authentication. On the side bar, option Providers shows up; if not, first activate Windows Authentication so it does show up;
  5. Remove NEGOTIATE provider.
  6. If you added Windows Authentication on step 4, deactivate it again;
  7. Do an IISReset

After performing the steps above, authentication should start working in Internet Explorer / Microsoft Edge.

 I tried lowering the priority of “NEGOTIATE” provider first, but that didn’t work unfortunately. Went ahead and removed it then tested again… It’s working in Edge without a UN/PW! Chrome still prompts the first time, but I maybe integrated security doesn’t work the same on Chrome ?? SSRS prompts for credentials in Chrome too if you haven’t authenticated already.

 And how I got there in case that was the wrong “fix” and it needs to be undone:





2/19/2023 6:39:09 AM | Web_Blog