738 reputation
11127
bio website twitter.com/#!/BenBrocka
location Iowa
age 24
visits member for 3 years, 3 months
seen Aug 21 at 21:19

I'm a moderator on User Experience Stack Exchange. (That's right here!)

Programmer/Systems Analyst working mostly in PHP/HTML/CSS. Enthusiast follower of User Experience topics and solutions.


Apr
18
accepted Select a single row from two distinct columns
Apr
18
accepted Top 2 rows per partition from an absolute value date difference
Apr
18
asked Identifying rows which don't match a master row
Apr
1
revised Upgrade process from SQL Server 2000 to SQL Server 2012
improved syntax but I still have no idea what this is trying to say...
Apr
1
suggested approved edit on Upgrade process from SQL Server 2000 to SQL Server 2012
Mar
7
comment Splitting Tables in MySQL. Good practice?
That sounds...horrifying.
Mar
1
comment Adding columns to production tables
Did you mean "doesn't" require adding data to the rows in your second line?
Feb
27
awarded  Outspoken
Feb
27
comment Speed up INSERTs
Your bottlenecks on the laptop are probably very different (and variable!) compared to a proper server. If you're going to stress test at least run it on a device set up as a server with nothing else running. You're likely to hit RAM/CPU bottlenecks on a laptop that might not exist on a production machine
Feb
23
accepted Why is IDENTITY_INSERT ON only allowed on one table at a time?
Feb
23
accepted Does ORDER BY on a clustered key effect performance?
Feb
14
awarded  Nice Question
Feb
13
comment Single Identity column and composite key, which to make primary?
I agree with this generally, but as JNK points out I really don't need my surrogate key to even be a key (as long as I don't fudge the uniqueness).
Feb
12
comment Why is IDENTITY_INSERT ON only allowed on one table at a time?
@AaronBertrand But again, the duplicate ID risk is exactly the same on any table with IDENTITY INSERT on, why the hard limit? I think the fact that it persists only for the connection makes much more sense as a precaution.
Feb
10
comment Why is IDENTITY_INSERT ON only allowed on one table at a time?
@AaronBertrand it's not, as I implied in the Q. Not sure about deterrent either, since SQL Server allows lots of other bad practices like naming your columns with reserved keywords (sometimes even if you don't use []!)
Feb
10
revised Why is IDENTITY_INSERT ON only allowed on one table at a time?
added 74 characters in body
Feb
10
comment Why is IDENTITY_INSERT ON only allowed on one table at a time?
@RemusRusanu that's kind of what I was thinking, either that or to make sure you don't accidentally leave II ON for multiple tables.
Feb
10
asked Why is IDENTITY_INSERT ON only allowed on one table at a time?
Feb
10
comment Single Identity column and composite key, which to make primary?
@JNK True...none of that helps updates does it. I shouldn't ever need to select on it
Feb
10
comment Single Identity column and composite key, which to make primary?
@JNK No, it's syntactic sugar for my framework. All queries are done based on the composite key because the IDENTITY doesn't exist in my source table. So far as I've designed, the IDENTITY is never used except to update rows via the framework. Queries make extensive use of the composite key though, hence the clustered index to match the source table.