Skip to content

Commit da25a19

Browse files
v-thepetv-thepet
committed
fix external links
1 parent 74268dd commit da25a19

17 files changed

Lines changed: 65 additions & 69 deletions

‎docs/2014/analysis-services/behavior-changes-to-analysis-services-features-in-sql-server-2014.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -34,7 +34,7 @@ manager: craigg
3434
|Issue|Description|
3535
|-----------|-----------------|
3636
|SQL Server 2008 R2 PowerPivot workbooks will not silently upgrade and refresh the models when they are used in SQL Server 2012 SP1 PowerPivot for SharePoint 2013. Therefore Scheduled data refreshes will not work for SQL Server 2008 R2 PowerPivot workbooks.|The 2008 R2 workbooks will open in [!INCLUDE[ssGeminiShortvnext](../includes/ssgeminishortvnext-md.md)], however scheduled refreshes will not work. If you review the refresh history you will see an error message similar to the following:<br /> "The workbook contains an unsupported PowerPivot model. The PowerPivot model in the workbook is in the SQL Server 2008 R2 PowerPivot for Excel 2010 format. Supported PowerPivot models are the following: <br />SQL Server 2012 PowerPivot for Excel 2010<br />SQL Server 2012 PowerPivot for Excel 2013"<br /><br /> **How to upgrade a workbook:** The scheduled refreshes will not work until you upgrade the workbook to a 2012 workbook. To upgrade the workbook and model it contains, complete one of the following:<br /><br /> Download and open the workbook in Microsoft Excel 2010 with the SQL Server 2012 PowerPivot for Excel add-in installed. Then save the workbook and republish it to the SharePoint server.<br /><br /> Download and open the workbook in Microsoft Excel 2013. Then save the workbook and republish it to the SharePoint server.<br /><br /> <br /><br /> For more information on workbook upgrade, see [Upgrade Workbooks and Scheduled Data Refresh &#40;SharePoint 2013&#41;](instances/install-windows/upgrade-workbooks-and-scheduled-data-refresh-sharepoint-2013.md).|
37-
|Behavior change in DAX [ALL Function](https://msdn.microsoft.com/library/ee634802(v=sql.120).aspx).|Prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)], if you specify a [Date] column in Mark as Date Table, for use in time-intelligence, and that [Date] column is passed as an argument to the ALL function, in-turn, passed as a filter to a CALCULATE function, all filters for all columns in the table are ignored, regardless of any slicer on the date column.<br /><br /> For example,<br /><br /> `= CALCULATE (<expression>, ALL (DateTable[Date]))`<br /><br /> Prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)], all filters are ignored for all columns of DateTable, regardless of the [Date] column passed as an argument to ALL.<br /><br /> In [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)] and in PowerPivot in Excel 2013, the behavior will ignore filters only for the specified column passed as an argument to ALL.<br /><br /> To work around the new behavior, in effect ignore all columns as a filter for the entire table, you can exclude [Date] column from the argument, for example,<br /><br /> `=CALCULATE (<expression>, ALL(DateTable))`<br /><br /> This will yield the same result as the behavior prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)].|
37+
|Behavior change in DAX [ALL Function](/dax/all-function-dax).|Prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)], if you specify a [Date] column in Mark as Date Table, for use in time-intelligence, and that [Date] column is passed as an argument to the ALL function, in-turn, passed as a filter to a CALCULATE function, all filters for all columns in the table are ignored, regardless of any slicer on the date column.<br /><br /> For example,<br /><br /> `= CALCULATE (<expression>, ALL (DateTable[Date]))`<br /><br /> Prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)], all filters are ignored for all columns of DateTable, regardless of the [Date] column passed as an argument to ALL.<br /><br /> In [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)] and in PowerPivot in Excel 2013, the behavior will ignore filters only for the specified column passed as an argument to ALL.<br /><br /> To work around the new behavior, in effect ignore all columns as a filter for the entire table, you can exclude [Date] column from the argument, for example,<br /><br /> `=CALCULATE (<expression>, ALL(DateTable))`<br /><br /> This will yield the same result as the behavior prior to [!INCLUDE[ssSQL11SP1](../includes/sssql11sp1-md.md)].|
3838

3939
## <a name="bkmk_sql2012"></a> Behavior Changes in [!INCLUDE[ssSQL11](../includes/sssql11-md.md)]
4040
This section documents the behavioral changes reported for [!INCLUDE[ssASnoversion](../includes/ssasnoversion-md.md)] features in [!INCLUDE[ssSQL11](../includes/sssql11-md.md)]. These changes also apply to [!INCLUDE[ssSQL14](../includes/sssql14-md.md)].

‎docs/2014/analysis-services/dax-formula-compatibility-in-directquery-mode-ssas-2014.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -79,7 +79,7 @@ Casts to the Boolean data type of any other string results in an error.
7979
**Cast from string to date/time**
8080
In DirectQuery mode, casts from string representations of dates and times to actual **datetime** values behave the same way as they do in SQL Server.
8181

82-
For information about the rules governing casts from string to **datetime** data types in [!INCLUDE[ssGemini](../includes/ssgemini-md.md)] models, see the [DAX Syntax Reference](https://msdn.microsoft.com/library/ee634217.aspx).
82+
For information about the rules governing casts from string to **datetime** data types in [!INCLUDE[ssGemini](../includes/ssgemini-md.md)] models, see the [DAX Syntax Reference](/dax/dax-syntax-reference
8383

8484
Models that use the in-memory data store support a more limited range of text formats for dates than the string formats for dates that are supported by SQL Server. However, DAX supports custom date and time formats.
8585

@@ -127,7 +127,7 @@ SQL Server handles nulls and blanks differently than the xVelocity engine. As a
127127

128128
The same limitations apply to the other logarithmic functions: LOG10 and LN.
129129

130-
For more information about the **blank** data type in DAX, see [DAX Syntax Reference](https://msdn.microsoft.com/library/ee634217.aspx).
130+
For more information about the **blank** data type in DAX, see [DAX Syntax Reference](/dax/dax-syntax-reference
131131

132132
**Division by 0 and division by Blank**
133133
In DirectQuery mode, division by zero (0) or division by BLANK will always result in an error. SQL Server does not support the notion of infinity, and because the natural result of any division by 0 is infinity, the result is an error. However, SQL Server supports division by nulls, and the result must always equal null.

‎docs/2014/analysis-services/powershell/technical-reference-ssas.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -32,7 +32,7 @@ manager: craigg
3232
![Small File Folder Icon](../../integration-services/media/filefolder-small.gif "Small File Folder Icon") **Query and Expression Language Reference**
3333
[Multidimensional Expressions &#40;MDX&#41; Reference](/sql/mdx/multidimensional-expressions-mdx-reference)
3434

35-
[Data Analysis Expressions &#40;DAX&#41; Reference](https://msdn.microsoft.com/library/gg413422(v=sql.120).aspx)
35+
[Data Analysis Expressions &#40;DAX&#41; Reference](/dax/data-analysis-expressions-dax-reference)
3636

3737
[Data Mining Extensions &#40;DMX&#41; Reference](/sql/dmx/data-mining-extensions-dmx-reference)
3838

‎docs/2014/analysis-services/tabular-models/calculations-ssas-tabular.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -20,7 +20,7 @@ manager: craigg
2020
|-----------|-----------------|
2121
|[Understanding DAX in Tabular Models &#40;SSAS Tabular&#41;](understanding-dax-in-tabular-models-ssas-tabular.md)|Describes the Data Analysis Expressions (DAX) formula language used to create calculations for calculated columns, measures, and row filters in tabular models.|
2222
|[Formula Compatibility in DirectQuery Mode](../dax-formula-compatibility-in-directquery-mode-ssas-2014.md)|Describes the differences, lists the functions that are not supported in DirectQuery mode, and lists the functions that are supported but could return different results.|
23-
|[Data Analysis Expressions &#40;DAX&#41; Reference](https://msdn.microsoft.com/library/gg413422(v=sql.120).aspx)|This section provides detailed descriptions of DAX syntax, operators, and functions.|
23+
|[Data Analysis Expressions &#40;DAX&#41; Reference](/dax/data-analysis-expressions-dax-reference)|This section provides detailed descriptions of DAX syntax, operators, and functions.|
2424

2525
> [!NOTE]
2626
> Step-by-step tasks for creating calculations are not provided in this section. Because calculations are specified in calculated columns, measures, and row filters (in roles), instructions on where to create DAX formulas are provided in tasks related to those features. For more information, see [Create a Calculated Column &#40;SSAS Tabular&#41;](ssas-calculated-columns-create-a-calculated-column.md), [Create and Manage Measures &#40;SSAS Tabular&#41;](measures-ssas-tabular.md), and [Create and Manage Roles &#40;SSAS Tabular&#41;](roles-ssas-tabular.md).

‎docs/2014/analysis-services/tabular-models/create-and-manage-roles-ssas-tabular.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ manager: kfile
6161
[Roles &#40;SSAS Tabular&#41;](roles-ssas-tabular.md)
6262
[Perspectives &#40;SSAS Tabular&#41;](perspectives-ssas-tabular.md)
6363
[Analyze in Excel &#40;SSAS Tabular&#41;](analyze-in-excel-ssas-tabular.md)
64-
[USERNAME Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh230954.aspx)
65-
[CUSTOMDATA Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh213140.aspx)
64+
[USERNAME Function &#40;DAX&#41;](/dax/username-function-dax)
65+
[CUSTOMDATA Function &#40;DAX&#41;](/dax/customdata-function-dax)
6666

6767

‎docs/2014/analysis-services/tabular-models/data-types-supported-ssas-tabular.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -62,7 +62,7 @@ manager: craigg
6262
> You cannot import from a **varchar(max)** column that contains a string length of more than 131,072 characters.
6363
6464
### Table Data Type
65-
In addition, DAX uses a *table* data type. This data type is used by DAX in many functions, such as aggregations and time intelligence calculations. Some functions require a reference to a table; other functions return a table that can then be used as input to other functions. In some functions that require a table as input, you can specify an expression that evaluates to a table; for some functions, a reference to a base table is required. For information about the requirements of specific functions, see [DAX Function Reference](https://msdn.microsoft.com/library/ee634396.aspx).
65+
In addition, DAX uses a *table* data type. This data type is used by DAX in many functions, such as aggregations and time intelligence calculations. Some functions require a reference to a table; other functions return a table that can then be used as input to other functions. In some functions that require a table as input, you can specify an expression that evaluates to a table; for some functions, a reference to a base table is required. For information about the requirements of specific functions, see [DAX Function Reference](/dax/dax-function-reference).
6666

6767
## <a name="bkmk_implicit"></a> Implicit and Explicit Data Type Conversion in DAX Formulas
6868
Each DAX function has specific requirements as to the types of data that are used as inputs and outputs. For example, some functions require integers for some arguments and dates for others; other functions require text or tables.
@@ -182,7 +182,7 @@ manager: craigg
182182
|BLANK OR BLANK|BLANK|Error|
183183
|BLANK AND BLANK|BLANK|Error|
184184

185-
For details on how a particular function or operator handles blanks, see the individual topics for each DAX function, in the section, [DAX Function Reference](https://msdn.microsoft.com/library/ee634396.aspx).
185+
For details on how a particular function or operator handles blanks, see the individual topics for each DAX function, in the section, [DAX Function Reference](/dax/dax-function-reference).
186186

187187
## See Also
188188
[Data Sources &#40;SSAS Tabular&#41;](../data-sources-ssas-tabular.md)

‎docs/2014/analysis-services/tabular-models/directquery-mode-ssas-tabular.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -76,7 +76,7 @@ manager: craigg
7676

7777
- **Client restrictions:** When a model is in DirectQuery mode, it can only be queried by using DAX. You cannot use MDX to create queries. This means that you cannot use the Excel Pivot Client, because Excel uses MDX.
7878

79-
However, you can create queries against a DirectQuery model in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] if you use a DAX table query as part of an XMLA Execute statement, For more information, see [DAX Query Syntax Reference](https://msdn.microsoft.com/library/ee634217.aspx).
79+
However, you can create queries against a DirectQuery model in [!INCLUDE[ssManStudioFull](../../includes/ssmanstudiofull-md.md)] if you use a DAX table query as part of an XMLA Execute statement, For more information, see [DAX Query Syntax Reference](/dax/dax-syntax-reference
8080

8181
When you have resolved all the design issues and tested your model, you are ready for deployment. At this point, you can set the preferred method for answering queries against the model. Do you want users to have access to the cache, or always use only the relational data source?
8282

‎docs/2014/analysis-services/tabular-models/roles-ssas-tabular.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -90,8 +90,8 @@ manager: craigg
9090

9191
|Function|Description|
9292
|--------------|-----------------|
93-
|[USERNAME Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh230954.aspx)|Returns the domain\ username of the user currently logged on.|
94-
|[CUSTOMDATA Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh213140.aspx)|Returns the CustomData property in a connection string.|
93+
|[USERNAME Function &#40;DAX&#41;](/dax/username-function-dax)|Returns the domain\ username of the user currently logged on.|
94+
|[CUSTOMDATA Function &#40;DAX&#41;](/dax/customdata-function-dax)|Returns the CustomData property in a connection string.|
9595

9696
You can use the LOOKUPVALUE function to return values for a column in which the Windows user name is the same as the user name returned by the USERNAME function or a string returned by the CustomData function. Queries can then be restricted where the values returned by LOOKUPVALUE match values in the same or related table.
9797

@@ -134,8 +134,8 @@ manager: craigg
134134
## See Also
135135
[Perspectives &#40;SSAS Tabular&#41;](perspectives-ssas-tabular.md)
136136
[Analyze in Excel &#40;SSAS Tabular&#41;](analyze-in-excel-ssas-tabular.md)
137-
[USERNAME Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh230954.aspx)
138-
[LOOKUPVALUE Function &#40;DAX&#41;](https://msdn.microsoft.com/library/gg492170.aspx)
139-
[CUSTOMDATA Function &#40;DAX&#41;](https://msdn.microsoft.com/library/hh213140.aspx)
137+
[USERNAME Function &#40;DAX&#41;](/dax/username-function-dax)
138+
[LOOKUPVALUE Function &#40;DAX&#41;](/dax/lookupvalue-function-dax)
139+
[CUSTOMDATA Function &#40;DAX&#41;](/dax/customdata-function-dax)
140140

141141

‎docs/2014/analysis-services/tabular-models/specify-mark-as-date-table-for-use-with-time-intelligence-ssas-tabular.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,6 +46,6 @@ manager: craigg
4646

4747
## See Also
4848
[Calculations &#40;SSAS Tabular&#41;](calculations-ssas-tabular.md)
49-
[Time Intelligence Functions &#40;DAX&#41;](https://msdn.microsoft.com/library/ee634763.aspx)
49+
[Time Intelligence Functions &#40;DAX&#41;](/dax/time-intelligence-functions-dax)
5050

5151

‎docs/2014/analysis-services/tabular-models/ssas-calculated-columns.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ manager: craigg
5454

5555
- When you rename a calculated column, any formulas that rely on the column must be updated manually. Unless you are in manual update mode, updating the results of formulas takes place automatically. However, this operation might take some time.
5656

57-
- There are some characters that cannot be used within the names of columns. For more information, see "Naming Requirements" in [DAX Syntax Specification for PowerPivot](https://msdn.microsoft.com/library/ee634217(v=sql.120).aspx).
57+
- There are some characters that cannot be used within the names of columns. For more information, see "Naming Requirements" in [DAX Syntax Specification for PowerPivot](/dax/dax-syntax-reference).
5858

5959
## <a name="bkmk_perf"></a> Performance of Calculated Columns
6060
The formula for a calculated column can be more resource-intensive than the formula used for a measure. One reason is that the result for a calculated column is always calculated for each row in a table, whereas a measure is only calculated for the cells defined by the filter used in a report, PivotTable, or PivotChart. For example, a table with a million rows will always have a calculated column with a million results, and a corresponding effect on performance. However, a PivotTable generally filters data by applying row and column headings; therefore, a measure is calculated only for the subset of data in each cell of the PivotTable.

0 commit comments

Comments
 (0)