737 reputation
515
bio website
location
age 32
visits member for 3 years
seen yesterday
sql must be lowercase.

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
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
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
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?
Aug
7
comment SSIS package blocks itself if uses TRUNCATE
@Kin sys.dm_exec_requests doesn't show what is blocking because it's -2. ValidateExternalMetadata solves the problem though, which is a bit surprising because all my OLE DB destinations already were 'Fast Load' which are said to be immune to the problem in the article.
Aug
7
comment SSIS package blocks itself if uses TRUNCATE
@Kin Just tried that, made no difference. As for truncating outside SSIS, I don't really know, because I don't really use distributed transactions outside SSIS; within a non-distributed transaction it works, obviously.
Aug
7
comment SSIS package blocks itself if uses TRUNCATE
@JonSeigel An interesting solution, will tuck away for future use, but will probably not apply here.
Jul
26
comment Passing NULL xml value to a certain CLR stored function crashes it when called in a certain way
@AaronBertrand I believe you misread the code; TestTest is scalar and is called as such, WillBeCalledByCLR is TV and is also called as such (with exists), no CLR-specific magic here. As for fixes, yes, the company is slow about fixes because they are believed to not only fix, but also amend and brake. Would actually be nice if this behaviour was confirmed as nonexistent on 2012, as it was last time.
Jul
26
comment Passing NULL xml value to a certain CLR stored function crashes it when called in a certain way
@AaronBertrand I call it from a case that returns single value, but even if I didn't scalar would still be okay as it is documented to return first value of first column and ignore the rest. Edited in version.
Dec
21
comment Inline table-valued function vs inline sql
the overall shape is quite different -- please be more specific here.
Oct
31
comment SQL Server 2008 Performance issue with very strange resolution
> In order to find out what is running or going on, I have to run a batch--which makes the problem stop. SO the act of trying to observe the issue resolves it.
Sep
6
comment CATCH block is triggered when it should not
@AlexKuznetsov Ultimately, errors that client must see are passed to the client. But there are errors that require internal work. Passing them to the client would imply relying on the client to do that work, and that breaks the incapsulation. The database is not an exclusive data storage only used by one application. Many types of clients can connect.
Sep
6
comment CATCH block is triggered when it should not
Makes sense to me. The context of a try block erroneously survives, so the error functions can return their values, and another consequence would be that an error brings execution into the handler of the erroneously survived try context.
Sep
6
comment CATCH block is triggered when it should not
@gbn Are you saying this is a bug in 2008 that has been fixed in 2012? Is there an entry on connect?
Sep
6
comment CATCH block is triggered when it should not
@gbn When specifically applied to transactions, yes, it does (the template is going to be a bit more complex though, as we have sort-of-okay errors that give XACT_STATE() = 1, so we rollback to a save point and carry on). But I'm more concerned about the very principle of error handling here, even when to transactions are present. Any code after commit_and_exit: is going to execute twice.
May
7
comment Associate a piece of data with a session
I'm happy with a separate table as long as I can clearly tell apart live data from expired data. SPID is not really good because it is reused, but if it is only used for nightly cleaning and not for fetching data, then it's going to be fine.
May
7
comment Associate a piece of data with a session
I thought about that, but then we're back to the problem of cleaning up expired data? No wait, we're not. The data will not delete itself, but will not get used by any subsequent connections... Yes, that's an option.