Business reason:
Primarily to avoid confusion in KPIs - data from one quarter (or year) can
get rolled into KPIs for the next quarter depending on the time dimension.
For example, if 10 purchase orders arrive at 11:30 PM 12/31/2006 in a
server that is located in PST, then they would roll up into 2006 numbers
for PST but 2007 numbers for EST,CST etc. That would be confusing. UTC
would ensure same numbers across timezones.
Additional Technical Reason:
OLAP data is pre-populated by DTS task. The aggregation page directly
connects to OLAP. So data would be consistent across all time zones; we
chose UTC over server timezone as it is normal practice to align everything
using UTC times.
--------------------
match
in
This posting is provided "AS IS" with no warranties, and confers no rights.
Connected Systems Division Team
Get Connected!
Meet and interact with key BizTalk Server program managers, developers, and
testers, and let them and other BizTalk Server community team members and
Most Valuable Professionals help you solve your product questions.
Navigate to http://msdn.microsoft.com/subscriptions/support/ in your
webrowser and register as a managed customer to receive MSDN Managed
Newsgroup Support!
MSDN managed newsgroups are available in English to MSDN Universal,
Enterprise, Professional, and Operating Systems subscribers to receive
free, unlimited technical support on select Microsoft technologies as well
as to share ideas with other subscribers.