225 reputation
19
bio website careers.stackoverflow.com/…
location
age 37
visits member for 2 years, 7 months
seen Oct 20 at 17:58

My Professional Profile.

My email: cmljYXJkb2phdmllcnNhbmNoZXpAZ21haWwuY29t - Come on, you should be able to recognize the encoding ;)

profile for Icarus on Stack Exchange, a network of free, community-driven Q&A sites


Jan
16
comment Raise error from Stored PROC in SQL Server PDW
This is an awesome hack and I am prepared to live with it. I will accept your answer. Thanks!
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
thank you for your answer.
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
@JonSeigel Getting rid of TryParseExact and using ParseExact only reduced the execution time by 1 sec (5 secs). Still slower than the T-SQL approach.
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
@JonSeigel I created a SQL CLR Function to test on my DEV environment (used DateTime.TryParseExact) and on 100K rows sample, performs twice slower than my T-SQL version (3s Vs 6 secs).
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
@JonSeigel CLR integration is not enabled, unfortunately. I thought about that possibility too.
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
@AaronBertrand Refund? That person(s) needs to pay for damages... Seriously though, the saddest part is that it was likely a decision made by either the "chief software architect" or worse, a group of senior developers. In any case, I don't want to know... :-/
Sep
12
comment Constructing datetime from 2 fields: one integer and a datetime
@AaronBertrand That is not a possibility. The database has billions of rows of trading data and several apps (matching and routing engines) write to the database using an int to represent the time of the day :-/
Jan
10
comment Efficient SQL database design for recording examples of a word
@Cory I agree and I thought of that and you are right, it's a dangerous design if not handled with care. I will remove the suggestion.
Sep
14
comment Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
@SQLKiwi thanks for your comment. Yes, I am aware of this and it's a valid scenario for me.
Sep
13
comment Creating non-clustered Index on Partitioned Table that already has an existing Primary Key
@jnk I tried option A and the f***ing thing ran for over 4 hours to then throw the same Exception. Apparently Col_1 is a partitioned column in the table so I must make it part of every index I create, clustered or non-clustered. The problem for me is that this has been trial and error since I don't even have access to see table definitions in that environment. At least I think I have a better understanding of what's going on now. :\