I’m back home after a 2-week Iceland vacation. Let’s catch up with your top-voted questions from https://pollgab.com/room/brento.
Here’s what we covered:
- 00:00 Start
- 02:04 Suresh: Hi Brent . Question about 128 GB memory limit for SQL server standard edition.If I set ‘Max SQL Server Memory’ to 228 GB on a 256 GB VM , SQL will use the additional 100 GB for anything other than buffer pool . Is that correct assumption ?
- 03:41 Jens Herrmann: Two 20-year-old databases without any clustered indexes. The key columns are uniqueidentifier and some int columns. A colleague of mine changed all the table key columns to clustered indexes, and everything became noticeably slower. Is it a bad Idea to have a clustered index?
- 04:52 PAul: A production database is approaching 16TB. Adding another datafile to the PRIMARY filegroup is a solution. Is there any (dis)advantage to creating a new Filegroup on a different drive and moving large tables/indexes to it?
- 07:07 TokTik: What are your top recommended books on SQL server performance tuning for someone planning to explore this field for the first time?
- 07:51 Gary: Hi B. We have a Prod db that periodically experiences hundreds of long LCK_M_X waits and blocking on the same proc. Oddly, every one of those waiting sessions and the lead blocker is a COMPILE wait on the proc’s objectid. No RECOMPILE used anywhere. Why is sql trying to compile?
- 09:22 MyTeaGotCold: My devs use temporal tables a lot. Can you tell me any horror stories about them? I hit a SQL Server bug with system-versioned tables today and I’m scared.
- 10:30 Bandhu: What’s your faith level in third party SQL backup software? Considering it to get table level restores since Microsoft won’t add this any time soon.
- 10:53 Archivist: I’m trying to make backups faster by making cold data read only. How do I decide if I should make an RO database, make archive tables in an RO filegroup, or partition tables and make part of them RO?
- 12:10 neil: A frequently used dashboard randomly chooses horrible plan and kills production server. I tried forcing plan with Query Store. Works for a while then fails, says the index it’s using no longer exists? But I didn’t drop any indexes that I know of. Not sure where to look next.
- 13:33 thetechguy23: The role of a DBA today seems very blurred, at least at my organisation. As well as “keeping the lights on” we’re often asked to develop integrations exchanging data using REST API’s and then own that process. Data comes from the database, right? Where do you stand on that?
1 Comment. Leave new
My favorite experience of “dumb things dropping a db object in code then recreate it later” was some vendor code where they dropped the PRIMARY KEY CONSTRAINT on the table, insert/update data, then recreate the primary key constraint…which was a composite key with an editable field in the application (Address Name!). So guess what…users couldn’t figure out why they were getting Save errors when they had the same address name for multiple addresses for the customer. We informed the vendor of this bug and they were shocked that their own app does that….*rolls eyes* Our solution was to make that field read-only once you create each address for the customer.