SQL Server 2008 : http://www.microsoft.com/downloads/details.aspx?displaylang=en&FamilyID=66ab3dbb-bf3e-4f46-9559-ccc6a4f9dc19
CU 1-7 after SP1 installation:
CU1: http://support.microsoft.com/kb/969099
CU2: http://support.microsoft.com/kb/970315
CU3: http://support.microsoft.com/kb/971491
CU4: http://support.microsoft.com/kb/973602
CU5: http://support.microsoft.com/kb/975977
CU6: http://support.microsoft.com/kb/977443
CU7: http://support.microsoft.com/kb/979065
Tuesday, April 13, 2010
Monday, February 8, 2010
Additional column on Report Builder
When you are using Report Builder, an additional column may added automatically. This colunm is entity key of the data.
Grouping keys are definitely there by design. It is important to group on the keys to ensure consistency in results. This column are actually Base64 encoded smashed entity keys, basically your integer keys with a couple extra bits of information added, encoded as Base64 (in the case of composite keys, all the key column values are combined into this single string value). These should be used in your grouping expressions to ensure accurate grouping when other columns may overlap.
Grouping keys are definitely there by design. It is important to group on the keys to ensure consistency in results. This column are actually Base64 encoded smashed entity keys, basically your integer keys with a couple extra bits of information added, encoded as Base64 (in the case of composite keys, all the key column values are combined into this single string value). These should be used in your grouping expressions to ensure accurate grouping when other columns may overlap.
Subscribe to:
Posts (Atom)