[Video] Office Hours: Hot Dog Fingers Edition

Videos
1 Comment

I strapped on my Apple Vision Pro, updated its OS, and recaptured my persona with the latest updates, and… it’s still pretty weird. Let’s go through your top-voted questions from https://pollgab.com/room/brento and have a laugh at my hot dog fingers.

I didn’t mention in the video, but I do have to say: the audio capture is AWESOME. The Vision Pro’s spatial microphones are so good.

Here’s what we covered:

  • 00:00 Start
  • 01:15 T-SQL Querying : How can I tell if an operator in an execution plan is done by the storage engine or not? For example, how can I measure the impact of I/O latency on key lookups?
  • 03:49 James R: I remember a while ago you mentioned a website that looks at what large businesses require in a product that uses a database and compares features across database products. I can’t for the life of me remember what it was, and have spent number of hours looking for it. Thanks!
  • 04:37 Fu Qiang: Do you see any issues with locating both temp db and windows page file on the ephemeral drive for Azure SQL VM?
  • 05:55 Dom: Hi Brent ! With your experience, what would you say it the % of business where they still use stacked instances and same question with non-default SQL port. Thank you A fan 🙂
  • 07:27 Janus: With mainstream support done for MSSQL 2019, is it time to move on to 2022? (And thanks for the blogpost “Which Version of SQL Server Should You Use?”)
  • 09:52 SouthernMost: Hi Brent, How can I horizontally scale our heavy OLTP database on-premises to offload writes across multiple databases? I’m looking for alternatives to partitioning and (MDTC). Is sharing hot tables between databases a viable solution?
Previous Post
SQL Server 2022 Finally Fixed a SQL Server 2008 Query Plan Bug!
Next Post
Announcing Our Anniversary Sale!

1 Comment. Leave new

  • With regards to your answer about “when to upgrade to SQL Server 2022”, I agree that waiting for 2025 as well to do our next set of upgrades from 2019. I’ll be looking for a rumored feature that will allow for table replication between databases (hopefully to/from Azure) from 2025. However, we run Availability Groups and as you may or may not be familiar in that space (I understand that is an area that you didn’t want to master), those AGs are built upon the pesky Failover Cluster which is OS dependent and can only move one OS at a time.

    However, I do plan to upgrade the underlying servers in our current Server2019/SQL2019 AGs (secondary first, failover, trailing secondary) to Server 2022/SQL2019 so I can then roll on new Server2025/SQL2025 servers into the AG and simply failover to them to complete my upgrade from SQL 2019 to SQL 2025.

    Something to pass along to your audience.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *

Fill out this field
Fill out this field
Please enter a valid email address.