Fixing build suggestions

Author: David-Engel

docs/connect/odbc/data-classification.md

@@ -21,7 +21,7 @@ manager: kenvh
 ## Overview
 For the purpose of managing sensitive data, SQL Server and Azure SQL Server introduced the ability to provide database columns with sensitivity metadata that allows the client application to handle different types of sensitive data (such as health, financial, etc.) in accordance with data protection policies.
 
-For more information on how to assign classification to columns, see [SQL Data Discovery and Classification](../../relational-databases/security/sql-data-discovery-and-classification.md?view=sql-server-2017).
+For more information on how to assign classification to columns, see [SQL Data Discovery and Classification](../../relational-databases/security/sql-data-discovery-and-classification.md).
 
 Microsoft ODBC Driver 17.2 allows the retrieval of this metadata via SQLGetDescField using the SQL_CA_SS_DATA_CLASSIFICATION field identifier.
 

docs/connect/oledb/ole-db-errors/errors.md

@@ -28,7 +28,7 @@ ms.author: v-daenge
 
  [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] can return multiple errors. An application can retrieve server errors one at a time by calling [IMultipleResults::GetResult](/previous-versions/windows/desktop/ms721289(v=vs.85)) combined with ISQLErrorInfo and IErrorRecords.  
 
- The OLE DB Driver for SQL Server exposes the OLE DB record-enhanced **IErrorInfo**, the custom **ISQLErrorInfo**, and the provider-specific [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) error object interfaces.  
+ The OLE DB Driver for SQL Server exposes the OLE DB record-enhanced **IErrorInfo**, the custom **ISQLErrorInfo**, and the provider-specific [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md) error object interfaces.  
 
  For information about tracing errors, see [Data Access Tracing](/previous-versions/sql/sql-server-2008/cc765421(v=sql.100)). For information about enhancements to error tracing added in [!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)], see [Accessing Diagnostic Information in the Extended Events Log](../../oledb/features/accessing-diagnostic-information-in-the-extended-events-log.md).  
 

docs/connect/oledb/ole-db-errors/information-in-error-interfaces.md

@@ -40,7 +40,7 @@ ms.author: v-daenge
 |Member function|Description|  
 |---------------------|-----------------|  
 |**GetBasicErrorInfo**|Fills an ERRORINFO structure with basic information about an error. An ERRORINFO structure contains members that identify the HRESULT return value for the error, and the provider and interface to which the error applies.|  
-|**GetCustomErrorObject**|Returns a reference on interfaces **ISQLErrorInfo,** and [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15).|  
+|**GetCustomErrorObject**|Returns a reference on interfaces **ISQLErrorInfo,** and [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md).|  
 |**GetErrorInfo**|Returns a reference on an **IErrorInfo** interface.|  
 |**GetErrorParameters**|The OLE DB Driver for SQL Server does not return parameters to the consumer through **GetErrorParameters**.|  
 |**GetRecordCount**|Count of error records available.|  

docs/connect/oledb/ole-db-errors/sql-server-error-detail.md

@@ -23,7 +23,7 @@ ms.author: v-daenge
 
 [!INCLUDE[Driver_OLEDB_Download](../../../includes/driver_oledb_download.md)]
 
-  The OLE DB Driver for SQL Server defines the provider-specific error interface [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15). The interface returns more detail about a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] error and is valuable when command execution or rowset operations fail.  
+  The OLE DB Driver for SQL Server defines the provider-specific error interface [ISQLServerErrorInfo](../ole-db-interfaces/isqlservererrorinfo-geterrorinfo-ole-db.md). The interface returns more detail about a [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] error and is valuable when command execution or rowset operations fail.  
 
  There are two ways to obtain access to **ISQLServerErrorInfo** interface.  
 

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpcolfmt-ole-db.md

@@ -116,7 +116,7 @@ HRESULT BCPColFmt(
  The method succeeded.  
 
  E_FAIL  
- A provider specific error occurred, for detailed information use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider specific error occurred, for detailed information use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_UNEXPECTED  
  The call to the method was unexpected. For example, the [IBCPSession::BCPInit](../../oledb/ole-db-interfaces/ibcpsession-bcpinit-ole-db.md) method was not called before calling this method.  

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpcolumns-ole-db.md

@@ -49,7 +49,7 @@ HRESULT BCPColumns(
  The method succeeded.  
 
  E_FAIL  
- A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_UNEXPECTED  
  The call to the method was unexpected. For example, the **BCPInit** method was not called before calling this method. Also occurs when this method is called more than once for a bulk copy operation.  

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpcontrol-ole-db.md

@@ -44,7 +44,7 @@ HRESULT BCPControl(
 |BCP_OPTION_ABORT|Stops a bulk-copy operation that is already in progress. You can call the **BCPControl** method with an *eOption* argument of BCP_OPTION_ABORT from another thread to stop a running bulk-copy operation. The *iValue* argument is ignored.|  
 |BCP_OPTION_BATCH|The number of rows per batch. The default is 0, which indicates all rows in a table when data is being extracted, or all rows in the user data file when data is being copied to [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)]. A value less than 1 resets BCP_OPTION_BATCH to the default.|  
 |BCP_OPTION_DELAYREADFMT|A Boolean, if set to true, will cause [IBCPSession::BCPReadFmt](../../oledb/ole-db-interfaces/ibcpsession-bcpreadfmt-ole-db.md) to read at execution. If false (the default), IBCPSession::BCPReadFmt will immediately read the format file. A sequence error will occur if **BCP_OPTION_DELAYREADFMT** is true and you call IBCPSession::BCPColumns or IBCPSession::BCPColFmt.<br /><br /> A sequence error will also occur if you call `IBCPSession::BCPControl(BCPDELAYREADFMT, (void *)FALSE))` after calling `IBCPSession::BCPControl(BCPDELAYREADFMT, (void *)TRUE)` and IBCPSession::BCPWriteFmt.<br /><br /> For more information, see [Metadata Discovery](../../oledb/features/metadata-discovery.md).|  
-|BCP_OPTION_FILECP|The *iValue* argument contains the number of the code page for the data file. You can specify the number of the code page, such as 1252 or 850, or one of the following values:<br /><br /> BCP_FILECP_ACP: data in the file is in the Microsoft Windows® code page of the client.<br /><br /> BCP_FILECP_OEMCP: data in the file is in the OEM code page of the client (default).<br /><br /> BCP_FILECP_RAW: data in the file is in the code page of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].|  
+|BCP_OPTION_FILECP|The *iValue* argument contains the number of the code page for the data file. You can specify the number of the code page, such as 1252 or 850, or one of the following values:<br /><br /> BCP_FILECP_ACP: data in the file is in the Microsoft Windows® code page of the client.<br /><br /> BCP_FILECP_OEMCP: data in the file is in the OEM code page of the client (default).<br /><br /> BCP_FILECP_RAW: data in the file is in the code page of [!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)].|  
 |BCP_OPTION_FILEFMT|The version number of the data file format. This can be 80 ([!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)]), 90 ([!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)]), 100 ([!INCLUDE[ssKatmai](../../../includes/sskatmai-md.md)] or [!INCLUDE[ssKilimanjaro](../../../includes/sskilimanjaro-md.md)]), or 110 ([!INCLUDE[ssSQL11](../../../includes/sssql11-md.md)]). 110 is the default. This is useful for exporting and importing data in formats that were supported by earlier version of the server.  For example, to import data obtained from a text column in a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server into a **varchar(max)** column in a [!INCLUDE[ssVersion2005](../../../includes/ssversion2005-md.md)] or later server, you should specify 80. Similarly, if you specify 80 while exporting data from a **varchar(max)** column, it will be saved just like text columns are saved in the [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] format, and can be imported into a text column of a [!INCLUDE[ssVersion2000](../../../includes/ssversion2000-md.md)] server.|  
 |BCP_OPTION_FIRST|The first row of data of the file or table to copy. The default is 1; a value less than 1 resets this option to its default.|  
 |BCP_OPTION_FIRSTEX|For BCP out operations, specifies the first row of the database table to copy into the data file.<br /><br /> For BCP in operations, specifies the first row of the data file to copy into the database table.<br /><br /> The *iValue* parameter is expected to be the address of a signed 64-bit integer that contains the value. The maximum value that can be passed to BCPFIRSTEX 2^63-1.|  
@@ -71,7 +71,7 @@ HRESULT BCPControl(
  The method succeeded.  
 
  E_FAIL  
- A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_UNEXPECTED  
  The call to the method was unexpected. For example, the [IBCPSession::BCPInit](../../oledb/ole-db-interfaces/ibcpsession-bcpinit-ole-db.md) method was not called before calling this function.  

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpexec-ole-db.md

@@ -47,7 +47,7 @@ HRESULT BCPExec(
  The method succeeded.  
 
  E_FAIL  
- A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider-specific error occurred; for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_UNEXPECTED  
  The call to the method was unexpected. For example, the **BCPInit** method was not called before calling this method. Also occurs if the operation has been aborted through using the BCP_OPTION_ABORT option, and the **BCPExec** method was called afterwards.  

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpinit-ole-db.md

@@ -76,7 +76,7 @@ HRESULT BCPInit(
  The method succeeded.  
 
  E_FAIL  
- A provider specific error occurred' for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider specific error occurred' for detailed information, use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_OUTOFMEMORY  
  Out-of-memory error.  

docs/connect/oledb/ole-db-interfaces/ibcpsession-bcpreadfmt-ole-db.md

@@ -49,7 +49,7 @@ HRESULT BCPReadFmt(
  The method succeeded.  
 
  E_FAIL  
- A provider-specific error occurred, for detailed information use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md?view=sql-server-ver15) interface.  
+ A provider-specific error occurred, for detailed information use the [ISQLServerErrorInfo](./isqlservererrorinfo-geterrorinfo-ole-db.md) interface.  
 
  E_OUTOFMEMORY  
  Out of memory error.