network profile
| bio | website | |
|---|---|---|
| location | Denver, CO | |
| age | ||
| visits | member for | 7 months |
| seen | yesterday | |
| stats | profile views | 3 |
SQL Developer BI/DBA
|
Oct 31 |
awarded | Scholar |
|
Oct 31 |
accepted | Index with multiple leaf levels |
|
Oct 31 |
comment |
Index with multiple leaf levels Thanks [SQL Kiwi]. I suspected that different allocation units may create additional leaf levels. I am going to experiment with removing LOB data types and see if that helps my performance. |
|
Oct 31 |
comment |
Index with multiple leaf levels [darin strait] - I am actually describing a composite index with three leaf levels (0) and two non leaf levels. One of the leaf levels has a avg_page_space_used_in_percent lower than suggested - 68.98%. PAD_INDEX is turned off. |
|
Oct 30 |
asked | Index with multiple leaf levels |
|
Oct 4 |
answered | Intent Exclusive (IX) Lock questions |
|
Oct 4 |
comment |
Intent Exclusive (IX) Lock questions NOLOCK was used for the sake of example in an effort to avoid an exclusive lock, and in production i actually set the isolation level. There was no other code but a simple "SELECT Column FROM TABLE" in the batch. |
|
Oct 4 |
awarded | Student |
|
Oct 4 |
asked | Intent Exclusive (IX) Lock questions |
