Reputation
772
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
6 15
Newest
 Taxonomist
Impact
~18k people reached

Apr
3
awarded  Taxonomist
Feb
17
comment Work queue with complex select and long processing: Ensuring concurrency
@JNK There are two problems with this kind of locking - 1) it needs to be done outside of the transaction, so it must be taken out of the stored procedure that does the job and put on the client side, which breaks incapsulation and trusts the client too much, and 2) when the client closes unexpectedly the row remains permanently locked, so there needs to be a watch mechanism to unlock them that would be clever enough to not give false positives and yet unlock promptly. Also there is no choosing on the client side, the client must be happy with the row the system thinks it should take.
Feb
16
asked Work queue with complex select and long processing: Ensuring concurrency
Dec
19
awarded  Yearling
Sep
24
awarded  Autobiographer
Aug
18
awarded  Popular Question
Jul
31
awarded  Popular Question
Jul
23
awarded  Popular Question
Jul
2
awarded  Curious
Dec
19
awarded  Yearling
Nov
29
comment How to get SQL Server 2012 to use the invariant culture in format()?
Apparently people found nchar(0) to be able to crash SQL Server.
Sep
18
comment Cast to date is sargable but is it a good idea?
I can't help noticing that LINQ2SQL generates SQL where cast(date_column as date) = 'value' when presented with C# similar to where obj.date_column.Date == date_variable.
Sep
15
comment How to get SQL Server 2012 to use the invariant culture in format()?
@JonSeigel Posted, edited in the link.
Sep
15
revised How to get SQL Server 2012 to use the invariant culture in format()?
+ Connect link
Sep
15
comment How to get SQL Server 2012 to use the invariant culture in format()?
I wonder if this should be posted to connect.misrosoft.com now.
Sep
15
comment How to get SQL Server 2012 to use the invariant culture in format()?
Very interesting, thank you.
Aug
18
awarded  Critic
Aug
17
comment How to get SQL Server 2012 to use the invariant culture in format()?
@AaronBertrand Omitting the third parameter, as documented, gives you the result formatted according to your connection language (SET LANGUAGE). Invariant culture is supposed to be invariant accross machines, which makes it perfect for serialization. So it's used on the SQL Server level when it comes to serializing data in some form or another, this includes generating an XML off a query. The 'g' was just an example, I'm not actually using that. And I can emulate the invariantness by escaping the special characters in the format string ('dd\/MM\/yyyy'), but that's not pretty.
Aug
17
asked How to get SQL Server 2012 to use the invariant culture in format()?
Aug
7
comment SSIS package blocks itself if uses TRUNCATE
While the asnwer solves the problem, it does not really connect the dots nicely (and while I think I did connect them, I'm not entirely sure). So let me restate: The problem is that truncate will take schema-stability locks in addition to data locks, whereas delete will only take data locks. When later SSIS goes to validate the schema, it hits the taken schema-stability lock and waits because the connection that verifies metadata is intentionally not enlisted in the distributed transaction. With delete there is no problem because no schema locks were taken in the first place. Correct?