Reputation
272
Top tag
Next privilege 300 Rep.
Create new tags
Badges
1 8
Newest
 Curious
Impact
~3k people reached

  • 0 posts edited
  • 0 helpful flags
  • 4 votes cast
Jul
14
comment Query strategies using SQL Server 2016 system-versioned temporal tables for Slowly-Changing Dimensions
Why is it necessary to count the number of changes per customer? Customers that change postal code during the year does add complexity to the query, but actually reporting on those changes doesn't seem to be required.
Jul
14
revised Query strategies using SQL Server 2016 system-versioned temporal tables for Slowly-Changing Dimensions
added 139 characters in body
Jul
11
awarded  Curious
Jul
11
revised Query strategies using SQL Server 2016 system-versioned temporal tables for Slowly-Changing Dimensions
added 26 characters in body
Jul
10
revised Query strategies using SQL Server 2016 system-versioned temporal tables for Slowly-Changing Dimensions
added 2 characters in body
Jul
10
asked Query strategies using SQL Server 2016 system-versioned temporal tables for Slowly-Changing Dimensions
Jul
1
comment concatenating columns from multiple unrelated 1-row resultsets
Good answer. I also thought of the comma syntax and knew it would work here but also that it was deprecated and should be avoided-- but I forgot that commas with no WHERE was a synonym for CROSS JOIN which works great for this case. Thanks for reminding me!
Jul
1
accepted concatenating columns from multiple unrelated 1-row resultsets
Jun
29
awarded  Editor
Jun
29
revised concatenating columns from multiple unrelated 1-row resultsets
Fixed code typo
Jun
28
asked concatenating columns from multiple unrelated 1-row resultsets
Jun
28
asked Dimensional Model for inheritance in dimensions
Sep
24
awarded  Autobiographer
Jul
9
comment Handling time zones in data mart/warehouse
@Zane - converting the range request to UTC only works for simple queries where the range is identical for the entire query. If your query includes entities in different timezones (e.g. "Yesterday's sales for every store" where each store is in a different timezone and you define "yesterday" in context of the store, not the client) then converting before querying won't work.
Jun
20
awarded  Popular Question
Dec
22
awarded  Yearling
Dec
22
awarded  Nice Question
Jul
31
awarded  Supporter
Jul
31
comment How does SQL Server know predicates are correlated?
great answer, very thorough. thanks!
Jul
31
accepted How does SQL Server know predicates are correlated?