Reputation
Next tag badge:
572/400 score
77/80 answers
Badges
8 104 163
Newest
 Enlightened
Impact
~1.6m people reached

Apr
22
revised Should we still be using QUOTENAME to protect from injection attacks?
added 758 characters in body
Apr
22
revised Should we still be using QUOTENAME to protect from injection attacks?
added 758 characters in body
Apr
22
answered Should we still be using QUOTENAME to protect from injection attacks?
Apr
22
awarded  Enlightened
Apr
22
awarded  Nice Answer
Apr
22
answered TempDB uses a lot of space in buffer pool
Apr
22
comment TempDB uses a lot of space in buffer pool
I'd poke around in the metadata views and see if you can find those allocation unit id anywhere as presumably they are getting eliminated in the join. You could also get a random pageid for one of them from the first query and look at the page with dbcc page to see if that sheds any light.
Apr
22
answered Grant select on tables with a specific naming pattern
Apr
22
comment UPDATE statement in a trigger occasionally updates some columns but not others
Why does your trigger reference RowId when that isn't in the table definition you have given us?
Apr
22
revised UPDATE statement in a trigger occasionally updates some columns but not others
added 54 characters in body
Apr
22
comment TempDB uses a lot of space in buffer pool
In the second query it looks like the query needs to take account of the type. Not just use ON p.partition_id = a.container_id as sometimes it should join on hobt_id instead. See msdn.microsoft.com/en-GB/library/ms189792.aspx
Apr
22
comment TempDB uses a lot of space in buffer pool
If you modify the first query to filter on database_id=2 and group by allocation_unit_id how does it compare with the second query grouped by the same thing?
Apr
22
comment Converting old SQL 2000 Non-Ansi code to SQL 2012 compatible
@RoniVered it's probably worth diffing the execution plan XML for "before" and "after" versions as well. If they are the same except statement text then all's good otherwise maybe things need more validation.
Apr
22
comment Unexpected CASE evaluation logic
FWIW SQL Server also has its quirks in this area where things don't quite work as advertised dba.stackexchange.com/a/12945/3690
Apr
22
revised Why can a SQL Server table not have more than one IDENTITY column?
Non deprecated version
Apr
22
revised Why can a SQL Server table not have more than one IDENTITY column?
added 131 characters in body
Apr
22
revised Why can a SQL Server table not have more than one IDENTITY column?
added 131 characters in body
Apr
22
answered Why can a SQL Server table not have more than one IDENTITY column?
Apr
22
answered Clustered Index Misunderstanding
Apr
21
comment FK Issue with Fact Table
That factTable is not at the granularity of a single tweet so tweetid doesn't belong there. What is tweet related to in it?