September 2, 2012 at 8:54 pm
My company wants to create a Financial Calendar Table which contains only the Fiscal Dates. The requirements is ti populate it with the following columns:
- DateKey
- Fiscal_Year
- Fiscal_Month
- Fiscal_Week
- Fiscal Week_Start_Date
- Fiscal_Week_End_Date
The rules for these columns are:
- DateKey has to be in the format YYYYMMDD
- Weeks begin from Monday - Sunday
- Financial Year begins on 01/Jul
- Financial Week begins from Monday , which means if 01/Jul falls on any other days, then we have to take the Monday of that week as the beginning of the financial week. e.g. If 01/Jul falls on Wednesday, then the beginning of week is 29/06
Can someone help me with this script?
September 3, 2012 at 12:09 am
rka (9/2/2012)
DateKey has to be in the format YYYYMMDD
In SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2012 at 9:35 am
Jeff Moden (9/3/2012)
rka (9/2/2012)
DateKey has to be in the format YYYYMMDDIn SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
Jeff I agree its pretty insane,
But I've seen this especially if the YYYYMMDD is converted to an INT eg 20120101 = 20,120,101.
Its been a frequent topic of discussion on various DW projects that I've worked on, prior to the Date Data type most of the calendar dims used the DateTime with the PK/SK column a CAST(CalendarDate as Int), again a pretty nasty way of doing this especially if you have a time element due to the rounding issues.
However, since 2008 I've been converted to Date Data type as the PK/SK and it seems to work very well.
_________________________________________________________________________
SSC Guide to Posting and Best Practices
September 4, 2012 at 2:17 pm
Jason-299789 (9/4/2012)
Jeff Moden (9/3/2012)
rka (9/2/2012)
DateKey has to be in the format YYYYMMDDIn SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
Jeff I agree its pretty insane,
But I've seen this especially if the YYYYMMDD is converted to an INT eg 20120101 = 20,120,101.
Its been a frequent topic of discussion on various DW projects that I've worked on, prior to the Date Data type most of the calendar dims used the DateTime with the PK/SK column a CAST(CalendarDate as Int), again a pretty nasty way of doing this especially if you have a time element due to the rounding issues.
However, since 2008 I've been converted to Date Data type as the PK/SK and it seems to work very well.
NP. Thanks for the feedback. I have to ask again, though... what have you tried that isn't working in your efforts to build this table?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2012 at 7:46 pm
Jason-299789 (9/4/2012)
Jeff Moden (9/3/2012)
rka (9/2/2012)
DateKey has to be in the format YYYYMMDDIn SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
Jeff I agree its pretty insane,
But I've seen this especially if the YYYYMMDD is converted to an INT eg 20120101 = 20,120,101.
Its been a frequent topic of discussion on various DW projects that I've worked on, prior to the Date Data type most of the calendar dims used the DateTime with the PK/SK column a CAST(CalendarDate as Int), again a pretty nasty way of doing this especially if you have a time element due to the rounding issues.
However, since 2008 I've been converted to Date Data type as the PK/SK and it seems to work very well.
A "DW" is a data warehouse which is an OLAP-type database, and these rules and keys might make sense there, because an OLAP database has different goals than an OLTP database, and thus a different (though related) modelling methodology, and therefore a different set of normal rules.
An OLAP database is designed to facilitate reporting, at the expense of other things, like diskspace and being able to maintain the data in real-time. OLTP databases on the other hand are designed to facilitate real-time data updates while insuring consistency and still be able to report on the data.
Because of these differences in goals, OLAP databases will frequently have highly redundant multi-discriminating key structures, like the one you suggest, because they can greatly facilitate reporting and summarization. But they are an anethema to an OLTP database because they introduce all kinds of problems with maintaining the consistency of the data and keys when trying to incrementally keep it up-to-date in real time.
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 4, 2012 at 10:50 pm
RBarryYoung (9/4/2012)
Jason-299789 (9/4/2012)
Jeff Moden (9/3/2012)
rka (9/2/2012)
DateKey has to be in the format YYYYMMDDIn SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
Jeff I agree its pretty insane,
But I've seen this especially if the YYYYMMDD is converted to an INT eg 20120101 = 20,120,101.
Its been a frequent topic of discussion on various DW projects that I've worked on, prior to the Date Data type most of the calendar dims used the DateTime with the PK/SK column a CAST(CalendarDate as Int), again a pretty nasty way of doing this especially if you have a time element due to the rounding issues.
However, since 2008 I've been converted to Date Data type as the PK/SK and it seems to work very well.
A "DW" is a data warehouse which is an OLAP-type database, and these rules and keys might make sense there, because an OLAP database has different goals than an OLTP database, and thus a different (though related) modelling methodology, and therefore a different set of normal rules.
An OLAP database is designed to facilitate reporting, at the expense of other things, like diskspace and being able to maintain the data in real-time. OLTP databases on the other hand are designed to facilitate real-time data updates while insuring consistency and still be able to report on the data.
Because of these differences in goals, OLAP databases will frequently have highly redundant multi-discriminating key structures, like the one you suggest, because they can greatly facilitate reporting and summarization. But they are an anethema to an OLTP database because they introduce all kinds of problems with maintaining the consistency of the data and keys when trying to incrementally keep it up-to-date in real time.
BWAA-HAAA!!!! Is that the long version for "storing dates as INTs or VARCHARs sucks"??? 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2012 at 5:48 pm
Jeff Moden (9/4/2012)
RBarryYoung (9/4/2012)
Jason-299789 (9/4/2012)
Jeff Moden (9/3/2012)
rka (9/2/2012)
DateKey has to be in the format YYYYMMDDIn SQL Server, that's a pretty insane requirement because that would make a character based date. Since you're using SQL Server 2008, you should either use DATETIME or DATE datatypes for such a thing.
I strongly recommmend you talk to the people that designed the table and suggest that they should probably change it.
As for actually building the table... what have you tried that's not working?
Jeff I agree its pretty insane,
But I've seen this especially if the YYYYMMDD is converted to an INT eg 20120101 = 20,120,101.
Its been a frequent topic of discussion on various DW projects that I've worked on, prior to the Date Data type most of the calendar dims used the DateTime with the PK/SK column a CAST(CalendarDate as Int), again a pretty nasty way of doing this especially if you have a time element due to the rounding issues.
However, since 2008 I've been converted to Date Data type as the PK/SK and it seems to work very well.
A "DW" is a data warehouse which is an OLAP-type database, and these rules and keys might make sense there, because an OLAP database has different goals than an OLTP database, and thus a different (though related) modelling methodology, and therefore a different set of normal rules.
An OLAP database is designed to facilitate reporting, at the expense of other things, like diskspace and being able to maintain the data in real-time. OLTP databases on the other hand are designed to facilitate real-time data updates while insuring consistency and still be able to report on the data.
Because of these differences in goals, OLAP databases will frequently have highly redundant multi-discriminating key structures, like the one you suggest, because they can greatly facilitate reporting and summarization. But they are an anethema to an OLTP database because they introduce all kinds of problems with maintaining the consistency of the data and keys when trying to incrementally keep it up-to-date in real time.
BWAA-HAAA!!!! Is that the long version for "storing dates as INTs or VARCHARs sucks"??? 😀
8^Þ
(heh)
[font="Times New Roman"]-- RBarryYoung[/font], [font="Times New Roman"] (302)375-0451[/font] blog: MovingSQL.com, Twitter: @RBarryYoung[font="Arial Black"]
Proactive Performance Solutions, Inc. [/font][font="Verdana"] "Performance is our middle name."[/font]
September 5, 2012 at 6:13 pm
These two articles might give you a method of doing what you desire.
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply