1,044 reputation
21035
bio website
location Sydney, Australia
age
visits member for 1 year, 11 months
seen Jul 16 at 2:11

May
15
awarded  Caucus
May
15
accepted Writing select result to a csv file
May
12
comment Data dictionary best practices in SQL Server 2008 r2
The post you referred me to(above) was a good starting point.Thanks for that.
May
2
accepted Image fades on the SSRS report
May
2
answered Image fades on the SSRS report
May
1
comment Image fades on the SSRS report
Thanks Jon. Saving it as png file fixed the issue.
Apr
30
asked Image fades on the SSRS report
Apr
23
awarded  Notable Question
Apr
2
awarded  Popular Question
Mar
6
awarded  Notable Question
Feb
26
comment Choosing the right algorithm in HashBytes function
@Paul: That's exactly right. Thanks for your further clarification.
Feb
26
comment Choosing the right algorithm in HashBytes function
Good, that's the way we'll try then. We can improve the performance also ensuring the data correctness (what we needed). Many thanks for your generous time and input.
Feb
26
accepted Choosing the right algorithm in HashBytes function
Feb
26
comment Choosing the right algorithm in HashBytes function
Well, I was hoping not to have collision on SHA1 (for example based on this link: en.wikipedia.org/wiki/SHA-1 en.wikipedia.org ). However now that we can not rely on that, it means we can't use any hash value comparison.
Feb
25
awarded  Critic
Feb
25
comment Choosing the right algorithm in HashBytes function
Thanks Jon. The requirements tolerates no collision. So I think SHA1 is a safer option. We thought about defining index, but it's not possible. Because the columns used for joining are of Nvarchar(max). Even if the size was defined(e.g.: Nvarchar(4000), I don't think defining index on such a long column was not acceptable by SQL Server. I would double check though.
Feb
25
accepted Microsoft Baseline Configuration Analyser on Production
Feb
24
comment Choosing the right algorithm in HashBytes function
We need to join two tables on two nvarchar(max) columns. As you can imagine the query takes along time to execute. We thought it would be better to keep the hashsum value of each nvarchar(max) data and do the join on the hash values rather than the nvarchar(max) values which are blobs. The question is which hash algorithm provides the uniqueness, so that we don't run into the risk of having one hash value for more than one nvarchar(max).
Feb
22
asked Choosing the right algorithm in HashBytes function
Feb
22
asked Microsoft Baseline Configuration Analyser on Production