Skip to content

Commit 0a5380c

Browse files
authored
Merge pull request #34067 from MicrosoftDocs/main
5/8/2025 AM Publish
2 parents 482c310 + 29f5c6e commit 0a5380c

7 files changed

Lines changed: 175 additions & 3 deletions

File tree

azure-sql/managed-instance/failover-group-configure-sql-mi.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -382,7 +382,7 @@ You can create a failover group between SQL Managed Instances in two different s
382382
- Azure portal doesn't support creating failover groups across different subscriptions.
383383

384384
> [!IMPORTANT]
385-
> Azure portal does not support creation of failover groups across different subscriptions. For failover groups across different subscriptions and/or resource groups, failover can't be initiated manually via the Azure portal from the primary SQL managed instance. Initiate it from the geo-secondary instance instead.
385+
> Creating a failover group between two instances in different resource groups or subscriptions is only supported with Azure PowerShell, or the REST API, and not the Azure portal or the Azure CLI.
386386
387387
## <a name="preventing-the-loss-of-critical-data"></a> Prevent loss of critical data
388388

@@ -493,7 +493,7 @@ When creating a new failover group, consider the following limitations:
493493
- Failover groups can't be created between two instances in the *same* Azure region.
494494
- An instance can participate only in one failover group at any moment.
495495
- A failover group can't be created between two instances that belong to different Azure tenants.
496-
- Creating a failover group between two instances in different resource groups or subscriptions is only supported with Azure PowerShell, or the REST API, and not the Azure portal or the Azure CLI. Once the failover group is created, it's visible in the Azure portal, and all operations are supported in the Azure portal or with the Azure CLI. Failover must be initiated from the secondary instance.
496+
- Creating a failover group between two instances in different resource groups or subscriptions is only supported with Azure PowerShell, or the REST API, and not the Azure portal or the Azure CLI. Once the failover group is created, it's visible in the Azure portal, and all operations are supported in the Azure portal or with the Azure CLI.
497497
- If initial seeding of all databases doesn't complete within 7 days, creating the failover group fails and all successfully replicated databases are deleted from the secondary instance.
498498
- Creating a failover group with an instance configured with a [managed instance link](managed-instance-link-feature-overview.md) is currently unsupported.
499499
- Failover groups can't be created between instances if any of them are in an instance pool.

docs/connect/toc.yml

Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -4094,6 +4094,8 @@
40944094
href: ../odbc/reference/syntax/sqlconfigdriver-function.md
40954095
- name: SQLCreateDataSource Function
40964096
href: ../odbc/reference/syntax/sqlcreatedatasource-function.md
4097+
- name: SQLCreateDataSourceExW Function
4098+
href: ../odbc/reference/syntax/sqlcreatedatasourceexw-function.md
40974099
- name: SQLGetConfigMode Function
40984100
href: ../odbc/reference/syntax/sqlgetconfigmode-function.md
40994101
- name: SQLGetInstalledDrivers Function
@@ -4162,6 +4164,11 @@
41624164
href: ../odbc/reference/syntax/sqlsetconnectinfo-function.md
41634165
- name: SQLSetDriverConnectInfo Function
41644166
href: ../odbc/reference/syntax/installation-and-configuration-wwi-oltp.md
4167+
- name: Tracing DLL API Reference
4168+
href: ../odbc/reference/syntax/tracing-dll-api-reference.md
4169+
items:
4170+
- name: TraceVSControl Function
4171+
href: ../odbc/reference/syntax/tracevscontrol-function.md
41654172
- name: ODBC Appendixes
41664173
href: ../odbc/reference/appendixes/odbc-appendixes.md
41674174
items:

docs/integration-services/install-windows/upgrade-integration-services-packages.md

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,8 @@ title: "Upgrade Integration Services Packages"
33
description: "Upgrade Integration Services Packages"
44
author: "MikeRayMSFT"
55
ms.author: "mikeray"
6-
ms.date: "03/14/2017"
6+
ms.reviewer: randolphwest
7+
ms.date: 05/07/2025
78
ms.service: sql
89
ms.subservice: integration-services
910
ms.topic: upgrade-and-migration-article
@@ -18,6 +19,9 @@ helpviewer_keywords:
1819

1920
When you upgrade an instance of [!INCLUDE[sql2008-md](../../includes/sql2008-md.md)] to the current release of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)], your existing [!INCLUDE[ssISversion10](../../includes/ssisversion10-md.md)] packages are not automatically upgraded to the package format that the current release [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] [!INCLUDE[ssISnoversion](../../includes/ssisnoversion-md.md)] uses. You will have to select an upgrade method and manually upgrade your packages.
2021

22+
> [!IMPORTANT]
23+
> When you upgrade [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)] to [!INCLUDE [sssql14-md](../../includes/sssql14-md.md)] or later versions, make sure that the original [!INCLUDE [sssql11-md](../../includes/sssql11-md.md)] instance is removed after the upgrade. If you are subscribed to [Extended Security Updates for SQL Server](../../sql-server/end-of-support/sql-server-extended-security-updates.md), you are billed for both instances.
24+
2125
For information on upgrading packages when you convert a project to the project deployment model, see [Deploy Integration Services (SSIS) Projects and Packages](../../integration-services/packages/deploy-integration-services-ssis-projects-and-packages.md)
2226

2327
## Selecting an Upgrade Method

docs/odbc/reference/syntax/odbc-reference.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -25,3 +25,5 @@ The following topics contain syntax and semantic information for all ODBC functi
2525
- [Translation DLL Function Reference](../../../odbc/reference/syntax/translation-dll-api-reference.md)
2626

2727
- [ODBC Service Provider Interface (SPI) Reference](../../../odbc/reference/syntax/odbc-service-provider-interface-spi-reference.md)
28+
29+
- [Tracing DLL API Reference](../../../odbc/reference/syntax/tracing-dll-api-reference.md)
Lines changed: 94 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,94 @@
1+
---
2+
title: "SQLCreateDataSourceExW Function"
3+
description: "SQLCreateDataSourceExW Function"
4+
author: corylaban
5+
ms.author: corylaban
6+
ms.date: "05/07/2025"
7+
ms.service: sql
8+
ms.subservice: connectivity
9+
ms.topic: reference
10+
f1_keywords:
11+
- "SQLCreateDataSourceExW"
12+
helpviewer_keywords:
13+
- "SQLCreateDataSourceExW function [ODBC]"
14+
apilocation: "odbccp32.dll"
15+
apiname: "SQLCreateDataSourceExW"
16+
apitype: "dllExport"
17+
---
18+
# SQLCreateDataSourceExW Function
19+
**Conformance**
20+
Version Introduced: ODBC 2.0
21+
22+
**Summary**
23+
**SQLCreateDataSourceExW** adds a data source programmatically.
24+
25+
> [!WARNING]
26+
> The `SQLCreateDataSourceExW` function is private and isn't meant to be used directly in your code.
27+
> Microsoft doesn't support the use of this field in a production application under any circumstance.
28+
29+
## Syntax
30+
31+
```cpp
32+
typedef enum tagDSNType
33+
{
34+
evCreateAnyDSN,
35+
evCreateMachineDSN,
36+
evCreateUserDSN,
37+
evCreateSystemDSN,
38+
evCreateFileDSN
39+
} DSN_TYPE;
40+
41+
#define DSNC_ATTEMPT_CONN 0x00000001
42+
#define DSNC_DRIVER_ONLY 0x00000002
43+
44+
typedef struct tagODBCDSNCreationInfoW
45+
{
46+
DWORD dwSize;
47+
HWND hwndParent;
48+
DSN_TYPE DSNType;
49+
DSN_TYPE DSNRestrictType;
50+
DWORD dwCIFlags;
51+
WCHAR szDSNName[_MAX_PATH + 1];
52+
LPWSTR szParentDir;
53+
} ODBC_CREATE_DATASOURCE_INFOW;
54+
55+
BOOL INSTAPI SQLCreateDataSourceExW(
56+
ODBC_CREATE_DATASOURCE_INFOW * pCreateDSInfoW);
57+
```
58+
59+
## Arguments
60+
*pCreateDSInfoW*
61+
[Input] A struct of type `ODBC_CREATE_DATASOURCE_INFOW` see comments for descriptions.
62+
63+
## Returns
64+
**SQLCreateDataSourceExW** returns TRUE if the data source is created. Otherwise, it returns FALSE. See [SqlCreateDataSource](./sqlcreatedatasource-function.md#diagnostics) for diagnostic info about error codes when this function returns FALSE.
65+
66+
## Comments
67+
The `ODBC_CREATE_DATASOURCE_INFOW` has the following fields:
68+
69+
*dwSize*
70+
A `DWORD` containing the size of the struct.
71+
72+
*hwndParent*
73+
A handle to the parent directory of the data source.
74+
75+
*DSNType*
76+
The type of DSN to create. See [About Drivers and Data Sources](../../admin/about-drivers-and-data-sources.md) to understand what these enums map to.
77+
78+
*DSNRestrictType*
79+
The least restricted DSN type allowed.
80+
81+
*dwCIFlags*
82+
A mask with bits for either `DSNC_ATTEMPT_CONN` or `DSNC_DRIVER_ONLY`.
83+
84+
*szDSNName*
85+
Data source name.
86+
87+
*szParentDir*
88+
The parent directory of the data source.
89+
90+
## Related Functions
91+
92+
|For information about|See|
93+
|---------------------------|---------|
94+
|Creating data sources|[SQLCreateDataSource](./sqlcreatedatasource-function.md)|
Lines changed: 48 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,48 @@
1+
---
2+
title: "TraceVSControl Function"
3+
description: "TraceVSControl Function"
4+
author: corylaban
5+
ms.author: corylaban
6+
ms.date: "05/07/2025"
7+
ms.service: sql
8+
ms.subservice: connectivity
9+
ms.topic: reference
10+
f1_keywords:
11+
- "TraceVSControl"
12+
helpviewer_keywords:
13+
- "TraceVSControl [ODBC]"
14+
apilocation: "odbctrac.dll"
15+
apiname: "TraceVSControl"
16+
apitype: "dllExport"
17+
---
18+
# TraceVSControl Function
19+
**Conformance**
20+
Version Introduced: ODBC 2.0
21+
22+
**Summary**
23+
**TraceVSControl** toggles Visual Studio tracing.
24+
25+
> [!WARNING]
26+
> The `TraceVSControl` function is private and isn't meant to be used directly in your code.
27+
> Microsoft doesn't support the use of this field in a production application under any circumstance.
28+
> Follow instructions in [Setting Tracing Options](../../../odbc/admin/setting-tracing-options.md)
29+
> to configure tracing.
30+
31+
## Syntax
32+
33+
```cpp
34+
RETCODE SQL_API TraceVSControl(DWORD dwControl);
35+
```
36+
37+
## Arguments
38+
*dwControl*
39+
[Input] A DWORD indicating whether to enable VS tracing. Call `TraceVSControl` with `0x1L` to turn on tracing and `0x0L` to turn off tracing.
40+
41+
## Returns
42+
Always returns SQL_SUCCESS.
43+
44+
## Related Information
45+
46+
|For information about|See|
47+
|---------------------------|---------|
48+
|Understanding ODBC tracing|[Setting Tracing Options](../../../odbc/admin/setting-tracing-options.md)|
Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
---
2+
title: "Tracing DLL API Reference"
3+
description: "Tracing DLL API Reference"
4+
author: corylaban
5+
ms.author: corylaban
6+
ms.date: "05/07/2025"
7+
ms.service: sql
8+
ms.subservice: connectivity
9+
ms.topic: reference
10+
---
11+
# Tracing DLL API Reference
12+
13+
This section describes the syntax of the tracing DLL API. The behavior of ODBC tracing is described in [Setting Tracing Options](../../admin/setting-tracing-options.md).
14+
15+
This section contains the following topics.
16+
- [TraceVSControl Function](../../../odbc/reference/syntax/tracevscontrol-function.md)
17+

0 commit comments

Comments
 (0)