You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: azure-sql/includes/passwordless/associate-managed-identity-cli.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -31,7 +31,7 @@ If you are working with Git Bash, be careful of path conversions when using full
31
31
32
32
# [Azure Spring Apps](#tab/spring-apps-identity)
33
33
34
-
You can assign a managed identity to an Azure Spring Apps instance with the [az spring app identity assign](/cli/azure/spring/app/identity) command.
34
+
You can assign a managed identity to your Azure Spring Apps instance using the [az spring app identity assign](/azure/spring-apps/basic-standard/how-to-manage-user-assigned-managed-identities?tabs=azure-cli&pivots=sc-standard) command command in the Azure CLI.
Copy file name to clipboardExpand all lines: azure-sql/includes/passwordless/service-connector-commands.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ You can use Service Connector to create a connection between an Azure compute ho
33
33
34
34
# [Azure Spring Apps](#tab/spring-connector)
35
35
36
-
If you're using Azure Spring Apps, use the [az spring connection](/cli/azure/spring/connection/create) command:
36
+
If you're using Azure Spring Apps, use the [az spring connection create](/azure/service-connector/quickstart-portal-spring-cloud-connection?tabs=using-Managed-Identity&pivots=azure-cli) command to establish a service connection via Azure CLI.
Contains information about the actions taken to manage data-tier applications (DAC). This table is stored in the **dbo** schema of the **msdb** database.
|**sequence_id**|**int**|Identifies a step within an action.|
27
-
|**instance_id**|**uniqueidentifier**|Identifier of the DAC instance. This column can be joined on the **instance_id** column in [dbo.sysdac_instances (Transact-SQL)](../../relational-databases/system-catalog-views/data-tier-application-views-dbo-sysdac-instances.md).|
|**action_type_name**|**varchar(19)**|Name of the action type:<br /><br /> **deploy**<br /><br /> **create**<br /><br /> **rename**<br /><br /> **detach**<br /><br /> **delete**|
30
-
|**dac_object_type**|**tinyint**|Identifier of the type of object affected by the action:<br /><br /> **0** = dacpac<br /><br /> **1** = login<br /><br /> **2** = database|
31
-
|**dac_object_type_name**|**varchar(8)**|Name of the type of object affected by the action:<br /><br /> **dacpac** = DAC instance<br /><br /> **login**<br /><br /> **database**|
32
-
|**action_status**|**tinyint**|Code identifying the current status of the action:<br /><br /> **0** = pending<br /><br /> **1** = success<br /><br /> **2** = fail|
33
-
|**action_status_name**|**varchar(11)**|Current status of the action:<br /><br /> **pending**<br /><br /> **success**<br /><br /> **fail**|
34
-
|**Required**|**bit**|Used by the [!INCLUDE[ssDE](../../includes/ssde-md.md)] when rolling back a DAC operation.|
35
-
|**dac_object_name_pretran**|**sysname**|Name of the object before the transaction containing the action is committed. Used only for databases and logins.|
36
-
|**dac_object_name_posttran**|**sysname**|Name of the object after the transaction containing the action is committed. Used only for databases and logins.|
37
-
|**sqlscript**|**nvarchar(max)**|[!INCLUDE[tsql](../../includes/tsql-md.md)] script that implements an action on a database or login.|
38
-
|**payload**|**varbinary(max)**|DAC package definition saved in a binary encoded string.|
39
-
|**Comments**|**varchar(max)**|Records the login of a user who accepted potential data loss in a DAC upgrade.|
40
-
|**error_string**|**nvarchar(max)**|Error message generated if the action encounters an error.|
41
-
|**created_by**|**sysname**|The login that launched the action that created this entry.|
42
-
|**date_created**|**datetime**|The date and time this entry was created.|
43
-
|**date_modified**|**datetime**|The date and time the entry was last modified.|
44
-
45
-
## Remarks
46
-
DAC management actions, such as deploying or deleting a DAC, generate multiple steps. Each action is assigned an action identifier. Each step is assigned a sequence number and a row in **sysdac_history_internal**, where the status of the step is recorded. Each row is created when the action step starts, and is updated as needed to reflect the status of the operation. For example, a deploy DAC action could be assigned **action_id** 12 and get four rows in **sysdac_history_internal**:
DAC operations, such as delete, do not remove rows from **sysdac_history_internal**. You can use the following query to manually delete the rows for DACs no longer deployed on an instance of the [!INCLUDE[ssDE](../../includes/ssde-md.md)]:
56
-
57
-
```sql
58
-
DELETEFROMmsdb.dbo.sysdac_history_internal
59
-
WHERE instance_id NOT IN
60
-
(SELECT instance_id
61
-
FROMmsdb.dbo.sysdac_instances_internal);
62
-
```
63
-
64
-
Deleting rows for active DACs does not impact DAC operations; the only impact is that you will not be able to report the full history for the DAC.
65
-
23
+
Contains information about the actions taken to manage data-tier applications (DAC). This table is stored in the `dbo` schema of the `msdb` database.
24
+
25
+
| Column name | Data type | Description |
26
+
| --- | --- | --- |
27
+
|`action_id`|**int**| Identifier of the action |
28
+
|`sequence_id`|**int**| Identifies a step within an action. |
29
+
|`instance_id`|**uniqueidentifier**| Identifier of the DAC instance. This column can be joined on the `instance_id` column in [dbo.sysdac_instances](../system-catalog-views/data-tier-application-views-dbo-sysdac-instances.md). |
|`dac_object_type`|**tinyint**| Identifier of the type of object affected by the action:<br /><br />`0` = dacpac<br />`1` = login<br />`2` = database |
33
+
|`dac_object_type_name`|**varchar(8)**| Name of the type of object affected by the action:<br /><br />- `dacpac` = DAC instance<br />- `login`<br />- `database`|
34
+
|`action_status`|**tinyint**| Code identifying the current status of the action:<br /><br />`0` = not started<br />`1` = pending<br />`2` = success<br />`3` = fail<br />`4` = rollback |
35
+
|`action_status_name`|**varchar(11)**| Current status of the action:<br /><br />- `not started`<br />- `pending`<br />- `success`<br />- `fail`<br />- `rollback`|
36
+
|`required`|**bit**| Used by the [!INCLUDE [ssDE](../../includes/ssde-md.md)] when rolling back a DAC operation. |
37
+
|`dac_object_name_pretran`|**sysname**| Name of the object before the transaction containing the action is committed. Used only for databases and logins. |
38
+
|`dac_object_name_posttran`|**sysname**| Name of the object after the transaction containing the action is committed. Used only for databases and logins. |
39
+
|`sqlscript`|**nvarchar(max)**|[!INCLUDE [tsql](../../includes/tsql-md.md)] script that implements an action on a database or login. |
40
+
|`payload`|**varbinary(max)**| DAC package definition saved in a binary encoded string. |
41
+
|`comments`|**varchar(max)**| Records the login of a user who accepted potential data loss in a DAC upgrade. |
42
+
|`error_string`|**nvarchar(max)**| Error message generated if the action encounters an error. |
43
+
|`created_by`|**sysname**| The login that launched the action that created this entry. |
44
+
|`date_created`|**datetime**| The date and time this entry was created. |
45
+
|`date_modified`|**datetime**| The date and time the entry was last modified. |
46
+
47
+
## Remarks
48
+
49
+
DAC management actions, such as deploying or deleting a DAC, generate multiple steps. Each action is assigned an action identifier. Each step is assigned a sequence number and a row in `sysdac_history_internal`, where the status of the step is recorded. Each row is created when the action step starts, and is updated as needed to reflect the status of the operation. For example, a deploy DAC action could be assigned `action_id` 12 and get four rows in `sysdac_history_internal`:
DAC operations, such as delete, don't remove rows from `sysdac_history_internal`. You can use the following query to manually delete the rows for DACs no longer deployed on an instance of the [!INCLUDE [ssDE](../../includes/ssde-md.md)]:
Deleting rows for active DACs doesn't affect DAC operations; the only effect is that you can't report the full history for the DAC.
68
+
66
69
> [!NOTE]
67
-
> Currently, there is no mechanism for deleting **sysdac_history_internal** rows on [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)].
68
-
69
-
## Permissions
70
-
Requires membership in the sysadmin fixed server role. Read-only access to this view is available to all users with permissions to connect to the master database.
> Currently, there's no mechanism for deleting `sysdac_history_internal` rows on [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)].
71
+
72
+
## Permissions
73
+
74
+
Requires membership in the **sysadmin** fixed server role. Read-only access to this view is available to all users with permissions to connect to the `master` database.
Copy file name to clipboardExpand all lines: docs/reporting-services/report-server-sharepoint/powershell-cmdlets-for-reporting-services-sharepoint-mode.md
-2Lines changed: 0 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -47,8 +47,6 @@ When you install SQL Server 2016 Reporting Services SharePoint mode, PowerShell
47
47
Add-PSSnapin Microsoft.SharePoint.PowerShell
48
48
```
49
49
50
-
For more information, see [Use Windows PowerShell to administer SharePoint 2013](/powershell/module/sharepoint-server/).
51
-
52
50
### Open the SharePoint Management Shell and run cmdlets
In [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)], this function returns the current database system date as a **date** value, without the database time and time zone offset. `CURRENT_DATE` derives this value from the underlying operating system on the [!INCLUDE [ssde-md](../../includes/ssde-md.md)] runs.
39
+
This function returns the current database system date as a **date** value, without the database time and time zone offset. `CURRENT_DATE` derives this value from the underlying operating system on the [!INCLUDE [ssde-md](../../includes/ssde-md.md)] runs.
40
40
41
41
> [!NOTE]
42
42
> `SYSDATETIME` and `SYSUTCDATE` have more precision, as measured by fractional seconds precision, than `GETDATE` and `GETUTCDATE`. The `SYSDATETIMEOFFSET` function includes the system time zone offset. You can assign `SYSDATETIME`, `SYSUTCDATETIME`, and `SYSDATETIMEOFFSET` to a variable of any of the date and time types.
@@ -49,8 +49,6 @@ See [Date and time data types and functions](date-and-time-data-types-and-functi
49
49
50
50
## Syntax
51
51
52
-
[!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] only:
53
-
54
52
```syntaxsql
55
53
CURRENT_DATE
56
54
```
@@ -77,18 +75,14 @@ These examples use the system functions that return current date and time values
77
75
78
76
```sql
79
77
SELECT SYSDATETIME(),
80
-
SYSDATETIMEOFFSET(),
81
-
SYSUTCDATETIME(),
82
-
CURRENT_TIMESTAMP,
83
-
GETDATE(),
84
-
GETUTCDATE(),
85
-
CURRENT_DATE;
78
+
SYSDATETIMEOFFSET(),
79
+
SYSUTCDATETIME(),
80
+
CURRENT_TIMESTAMP,
81
+
GETDATE(),
82
+
GETUTCDATE(),
83
+
CURRENT_DATE;
86
84
```
87
85
88
-
> [!NOTE]
89
-
> [CURRENT_DATE (Transact-SQL)](current-date-transact-sql.md) is available in [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] only.
> [CURRENT_DATE (Transact-SQL)](current-date-transact-sql.md) is available in [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] only.
Copy file name to clipboardExpand all lines: docs/t-sql/functions/dateadd-transact-sql.md
+7-12Lines changed: 7 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ description: DATEADD returns a date modified by the specified date part.
4
4
author: markingmyname
5
5
ms.author: maghan
6
6
ms.reviewer: randolphwest
7
-
ms.date: 05/19/2025
7
+
ms.date: 08/25/2025
8
8
ms.service: sql
9
9
ms.subservice: t-sql
10
10
ms.topic: reference
@@ -33,10 +33,6 @@ This function adds a *number* (a signed integer) to a *datepart* of an input *da
33
33
34
34
See [Date and time data types and functions](date-and-time-data-types-and-functions-transact-sql.md) for an overview of all [!INCLUDE [tsql](../../includes/tsql-md.md)] date and time data types and functions.
35
35
36
-
> [!NOTE]
37
-
> `DATEADD` is available in Azure SQL Managed Instance configured with the [Always-up-to-date](/azure/azure-sql/managed-instance/update-policy#always-up-to-date-update-policy) update policy.
@@ -51,9 +47,6 @@ DATEADD (datepart , number , date )
51
47
52
48
The part of *date* to which `DATEADD` adds an **int***number*.
53
49
54
-
> [!NOTE]
55
-
> In [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] and [!INCLUDE [fabric](../../includes/fabric-sqldb.md)], *number* can be expressed as a **bigint**. This feature is in preview.
56
-
57
50
This table lists all valid *datepart* arguments. `DATEADD` doesn't accept user-defined variable equivalents for the *datepart* arguments.
58
51
59
52
|*datepart*| Abbreviations |
@@ -77,7 +70,7 @@ This table lists all valid *datepart* arguments. `DATEADD` doesn't accept user-d
77
70
An expression that can resolve to an [int](../data-types/int-bigint-smallint-and-tinyint-transact-sql.md) that `DATEADD` adds to a *datepart* of *date*. `DATEADD` accepts user-defined variable values for *number*. `DATEADD` truncates a specified *number* value that has a decimal fraction. It doesn't round the *number* value in this situation.
78
71
79
72
> [!NOTE]
80
-
> In [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [fabric](../../includes/fabric-sqldb.md)], *number* can be expressed as a **bigint**. This feature is in preview.
73
+
> In [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] and [!INCLUDE [fabric](../../includes/fabric-sqldb.md)], *number* can be expressed as a **bigint**. This feature is in preview.
These statements both return the following error message:
130
123
131
124
```output
132
-
Msg 8115, Level 16, State 2, Line 1. Arithmetic overflow error converting expression to data type int.
125
+
Msg 8115, Level 16, State 2, Line 1
126
+
Arithmetic overflow error converting expression to data type int.
133
127
```
134
128
135
129
> [!NOTE]
136
-
> In [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)] and [!INCLUDE [fabric](../../includes/fabric-sqldb.md)], *number* can be expressed as a **bigint**. This feature is in preview.
130
+
> In [!INCLUDE [sssql25-md](../../includes/sssql25-md.md)], [!INCLUDE [ssazure-sqldb](../../includes/ssazure-sqldb.md)], [!INCLUDE [ssazuremi-md](../../includes/ssazuremi-md.md)] and [!INCLUDE [fabric](../../includes/fabric-sqldb.md)], *number* can be expressed as a **bigint**. This feature is in preview.
0 commit comments