SQL Server Performance Office Hours Episode 2
What evils come of vertically partitioning a table into multiple tables? I have bad history with two of the alternatives. The first being long thin tables with foreign keys to what ought to have been their columns and the second being tables with too many columns. |
How can I keep our devs happy by avoiding stored procedures and embracing their preferred ORM (GORM in this case)? Not a big fan of ORMs. |
test after adding a field |
I got a table with only 2 columns, bigint and varbinary. For some reason app inserts a row in the table and after that updates the varbinary field with a value (likely a blob). I’m seeing blocking because of this. Any recommendation to mitigate it? |
Will you be at SQL Bits this year? |
To ask your questions, head over here.
Going Further
If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that, and need to solve database performance problems quickly. You can also get a quick, low cost health check with no phone time required.