Reputation
2,927
Top tag
Next privilege 3,000 Rep.
Cast close & reopen votes
Badges
1 9 33
Impact
~104k people reached

4h
comment bug in sp_rename
@Spörri what do you mean by that? I can imagine that cached plans might show wrong names but they should never come to execution again and access wrong tables.
May
2
answered Is there an advantage to not partition aligning an index?
Apr
27
awarded  Nice Question
Apr
27
comment What exactly can SQL Server 2014 execute in batch mode?
@ypercube that adds the runtime cost of moving rows through a row-mode loop join with one outer row. The LEFT JOIN trick is completely free.
Apr
27
accepted What exactly can SQL Server 2014 execute in batch mode?
Apr
27
comment What exactly can SQL Server 2014 execute in batch mode?
Thanks! I'd like to contribute the following trick: Simply add LEFT JOIN EmptyColumnstoreDummyTable ON 0=1 anywhere. This turns on Mixed Mode Execution and the join is completely removed by the optimizer. It does not add runtime cost.
Apr
26
comment SQL Server 2008 R2 error on database engine
Method 2 really needs the disclaimer that it can hose the instance.
Apr
26
reviewed Approve SQL Server 2008 R2 error on database engine
Apr
19
answered Indexes in a big table. (About 400 mil of rows)
Apr
19
comment effective mysql table/index design for 35 million rows+ table, with 200+ corresponding columns (double), any combination of which may be queried
"Moving to an enterprise system" is not a solution to this technical problem.
Apr
19
comment Indexes in a big table. (About 400 mil of rows)
What are you optimizing for? Read speed? Write speed? Disk space used? Pick priorities.
Apr
19
revised What is stored in a transaction log file?
deleted 16 characters in body; edited tags
Apr
12
asked What exactly can SQL Server 2014 execute in batch mode?
Apr
6
comment Estimated versus actual query plan with function calls
@MartinSmith yes, that one. It was "fixed" a 1-2 ago. I really hope I don't have to query the query store. I had hoped to click a button in SSMS. Actually, I was surprised to see any change at all to a part of the engine that wasn't touched in years. But maybe there was none.
Apr
6
comment The operating system returned error 665(The requested operation could not be completed due to a file system limitation) on SQL Server 2014
@Toni you can delete them. If you really want to be sure, rename them and let them sit for a few days.
Apr
6
awarded  Nice Question
Apr
6
comment Estimated versus actual query plan with function calls
@MartinSmith that might be a reason. Recently a connect item for execution plans of check and fk constraints was marked as completed so I was hopeful they would do the same thing with triggers.
Apr
6
comment Estimated versus actual query plan with function calls
@PaulWhite is there any good reason that trigger plans are not shown when requesting the estimated execution plan? That seems like a useful missing feature. I might create a connect item for it.
Apr
6
reviewed Approve The operating system returned error 665(The requested operation could not be completed due to a file system limitation) on SQL Server 2014
Apr
6
comment SQL Server index causing incorrect behavior on cursors
@MartinSmith I did not know that. What an insidious problem. It is impossible to test for since it can appear out of nowhere in case of a plan change. This shows again how nice set-based DML is compared to cursors. The logical model is much simpler.