| Stable release | Analysis Services 2016 / This purpose of the {{release date}} template is to return the date (or date-time) that an event or entity started or was created, and to do so in a standard format. It also includes duplicate, machine-readable date (or date-time) in the ISO date format (which is hidden by CSS), for use inside other templates (or table rows) which emit microformats. It should be used only once in each such template and never used outside such templates. The hidden date degrades gracefully when CSS is not available. When not to use this template[edit]Do not use this template for: - dates that are uncertain e.g., "before 4 April 1933"; "around 18 November 1939".
- dates outside the range given under "Limitation", below.
- other, secondary dates
- outside microformat-emitting templates - if in doubt, see the parent template's documentation
- more than one date in any parent template
- dates displayed using AM/PM format - this template only outputs 24-hour clocks
{{release date|year|month|day}}{{release date|year|month|day|HH|MM|SS|TimeZone}}(MM and SS are optional; TimeZone may be a numerical value, or "Z" for UTC; see examples)
- Examples
An optional parameter, df, can be set to "y" or "yes" (or indeed any value) to display the day before the month. The order of parameters does not change (it remains YMD). This is primarily used in articles using DMY format for dates. - Examples
TemplateData[edit]Template parameters |
| YYYY | 1 | start year
| Number | optional |
|---|
| MM | 2 | start month
| Number | optional |
|---|
| DD | 3 | start day of month
| Number | optional |
|---|
| HH | 4 | start hours
| Number | optional |
|---|
| MM | 5 | start minutes - Default
- 0
| Number | optional |
|---|
| SS | 6 | start seconds - Default
- 0
| Number | optional |
|---|
| TZ | 7 | time zone offset, “+02:00”, “-06:00” or “Z” for UTC
| Line | optional |
|---|
| day first | df | boolean parameter to put the day before the month name - Default
- false
| Line | optional |
|---|
| month first | mf | mf=yes: order mm-dd-yyyy (=the default order) - Default
- yes
| String | deprecated |
|---|
Use in microformats[edit]This template also returns the date, hidden by CSS, in the ISO 8601 format needed by one or more of the following microformats: usually, but not always, within infobox or similar templates, or tables. Its use in hCard is for organizations, venues and similar; use {{Birth date}} or {{Birth date and age}} for people. Similarly, {{End date}} returns the date as hCalendar's (class="dtend"). See the microformats project for further details. Limitation[edit]This template has no provision to deal with a date in a non-Gregorian calendar. Also, ISO 8601 requires mutual agreement among those exchanging information before using years outside the range 1583–9999 CE. Therefore, use of this template for non-Gregorian dates or dates outside that range constitutes a false claim of conformance to the ISO 8601 standard. Any editor encountering such usage should change the date to plain text with no template; or if not confident in doing so, raise the matter on this template's talk page. Example[edit]See also[edit]| hide Birth, death and age templates |
|---|
| show birth, death, age |
|---|
| show age only |
|---|
Microsoft SQL Server Analysis Services (SSAS[1]) is an online analytical processing (OLAP) and data miningtool in Microsoft SQL Server. SSAS is used as a tool by organizations to analyze and make sense of information possibly spread out across multiple databases, or in disparate tables or files. Microsoft has included a number of services in SQL Server related to business intelligence and data warehousing. These services include Integration Services, Reporting Services and Analysis Services. Analysis Services includes a group of OLAP and data mining capabilities and comes in two flavors - Multidimensional and Tabular. History[edit]In 1996, Microsoft began its foray into the OLAP Server business by acquiring the OLAP software technology from Canada-based Panorama Software.[2] Just over two years later, in 1998, Microsoft released OLAP Services as part of SQL Server 7. OLAP Services supported MOLAP, ROLAP, and HOLAP architectures, and it used OLE DB for OLAP as the client access API and MDX as a query language. It could work in client-server mode or offline mode with local cube files.[3] In 2000, Microsoft released Analysis Services 2000. It was renamed from "OLAP Services" due to the inclusion of data mining services. Analysis Services 2000 was considered an evolutionary release, since it was built on the same architecture as OLAP Services and was therefore backward compatible with it. Major improvements included more flexibility in dimension design through support of parent child dimensions, changing dimensions, and virtual dimensions. Another feature was a greatly enhanced calculation engine with support for unary operators, custom rollups, and cell calculations. Other features were dimension security, distinct count, connectivity over HTTP, session cubes, grouping levels, and many others.[4] In 2005, Microsoft released the next generation of OLAP and data mining technology as Analysis Services 2005. It maintained backward compatibility on the API level: although applications written with OLE DB for OLAP and MDX continued to work, the architecture of the product was completely different. The major change came to the model in the form of UDM - Unified Dimensional Model.[5][clarification needed] |
|
|
|
|---|
Comments
Post a Comment