Need to create U.S holiday Calendar in Snowflake to use for Date Dimension
Related
I have two tables I want to be able to join. One has dates in the format "2019-11-20", and there are instances on a daily basis. The other table contains weekly runs of a model in the format "2020-02-01 15:16:17.192837" How do i join these tables so that the daily occurrences are linked up with the weekly model runs?
If the columns are of type date and datetime, you can "cast" the datetime on the ON clause as in ON SimpleDate = Cast(ADateTime as date)
I'm trying to create some measures using DAX on an underlying data model which I would then use for creating some visuals (line chart, bar chart etc.). Each table in the data model has a data field (date&time) that contains repeated dates and times (more occurencies with the same date&time). To use the metrics in the visuals I need the measures to be grouped for date (only date, not for time).
To achieve the task I've created a calendar table (using CALENDAR in DAX) to set-up a set of dates (only dates) to which refer at for every table in the data model and created relations (dates that points to calendar date) for every table. I set the upper limit of the calendar table to be a year ahead of the max date in the dataset, because some measures need to be evaluated in the future.
In the visual pages, I put a slicer that points to the calendar table dates, but the date interval is too wide. I need the slicer to have a more narrow interval, let's say, only "for the present and the past" but I prefer not to add another calculated table.
In your opinion, is there a way to limit the slicer without changing its reference to the calendar table?
Thanks!
For the calendar you may just use CALENDARAUTO(). It will expand automatically as the data model expands.
For the slicer, just select it, open the filter pane and define a filter with the upper limit you want.
You can use combination of 3 different slicer for your purpose. This is just another option that you can have a look on. There will be 3 slicer for Year, Month & Date. So Date slicer is you final slicer, with 2 other slicer on top of it to generate necessary Dates in the slicer. This way, you are not making any static restriction to generate the Date list but giving the user full control on the Date range. Here below is a sample how the slicers can be look in practical.
User can select any year or multiple year, any month or multiple month. Finally the date slicer will hold Date values accordingly.
I am fetching a stored procedure to the report having two columns as date and non business day. I need to create a year wise calendar for the year which is getting fetched from stored procedure. Each page will have a calendar of a year with 12 months along with days.
Well, you would need a dataset with a Date (Day and Year at least) and a corresponding value for this Day. Then simply add a matrix in your report. For the columns textbox chose the Date (Day) and for the rows textbox chose the Date (Year). In the data textbox use your value. If you load it, it will look like calender because the Days get brocke down by Year.
In Cognos Framework, what should I use to retrieve week from a date instead of DATEPART? I do not want to follow ISO. I want 1/02/2016 to be Week 6.
If you want to follow a business calendar, you need to setup a calendar table. One record per date, each record has week number in Calendar year, and week number in fiscal year, and week number in month (calendar and fiscal). You can setup multiple calendars this way (for example if your marketing week is seperate from your accounting week, etc). Also a great place to setup relative date fields (which simplify alot of cognos reporting).
I have a table called "Publicholidays" where in dates are stored as Varchar.
My query should fetch all values from say table xxxx between the user selected dates that exclude the weekends(sat,sun), public holidays. I am new to DB2 so can anyone suggest me ideas please
Note: in DB dates are stored as String.
Mistake #1 - Storing dates as strings. Let's hope you have at least stored them YYYY-MM-DD and not MM-DD-YYYY.
Mistake #2 - Instead of a "Publicholidays" table, you need a Calendar (aka Dates or date conversion) table. It should have a record for every day along with a few flag columns BUSINESS_DAY, WEEKEND, PUBLIC_HOLIDAY. Alternatively, you could have a single DAY_TYPE column with values for business day, weekend and holiday. You'll also want to have a STRING_DATE column to make conversion between your string date and a true date easier.
Google SQL Calender table and you'll find lots of examples and discussions.
Lastly, strongly consider fixing your DB to store dates in a date column.