meta user
network profile
| bio | website | |
|---|---|---|
| location | Sydney, Australia | |
| age | ||
| visits | member for | 9 months |
| seen | yesterday | |
| stats | profile views | 43 |
|
1d |
comment |
How to add rows/columns to the table in runtime in SSRS 2008 That's what I expected too but the current issue is when there are multiple courses, the original record gets repeated per course. Which is not what we need. Only the Course rows should be added, not the whole student record. I have a row group on StudentId, but it does not help. |
|
2d |
asked | How to add rows/columns to the table in runtime in SSRS 2008 |
|
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 29 |
asked | SSRS Reports Design Standards and Guidelines Document |
|
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 |
