|-------------|------|-------------|

| action_id | **varchar(4)** | ID of the action. Not nullable. |

| additional_information | **nvarchar(4000)** | Unique information that only applies to a single event is returned as XML. A small number of auditable actions contain this kind of information.<br /><br /> One level of TSQL stack will be displayed in XML format for actions that have TSQL stack associated with them. The XML format will be:<br /><br /> `<tsql_stack><frame nest_level = '%u' database_name = '%.*s' schema_name = '%.*s' object_name = '%.*s' /></tsql_stack>`<br /><br /> Frame nest_level indicates the current nesting level of the frame. The Module name is represented in three part format (database_name, schema_name and object_name). The module name will be parsed to escape invalid xml characters like `'\<'`, `'>'`, `'/'`, `'_x'`. They will be escaped as `_xHHHH\_`. The HHHH stands for the four-digit hexadecimal UCS-2 code for the character<br /><br /> Is nullable. Returns NULL when there is no additional information reported by the event. |

| audit_file_offset | **bigint** | **Applies to**: SQL Server only<br /><br /> The buffer offset in the file that contains the audit record. Is not nullable. |

| audit_schema_version | **int** | Always 1 |

| class_type | **varchar(2)** | The type of auditable entity that the audit occurs on. Is not nullable. |

| database_name | **sysname** | The database context in which the action occurred. Is nullable. Returns NULL for audits occurring at the server level. |

| database_principal_id | **int** |ID of the database user context that the action is performed in. Is not nullable. Returns 0 if this does not apply. For example, a server operation.|

| database_principal_name | **sysname** | Current user. Is nullable. Returns NULL if not available. |

| event_time | **datetime2** | Date and time when the auditable action is fired. Is not nullable. |

| file_name | **varchar(260)** | The path and name of the audit log file that the record came from. Is not nullable. |

| is_column_permission | **bit** | Flag indicating if this is a column level permission. Is not nullable. Returns 0 when the permission_bitmask = 0.<br /> 1 = true<br /> 0 = false |

| object_id | **int** | The ID of the entity on which the audit occurred. This includes the following:<br /> Server objects<br /> Databases<br /> Database objects<br /> Schema objects<br /> Is not nullable. Returns 0 if the entity is the Server itself or if the audit is not performed at an object level. For example, Authentication. |

| object_name | **sysname** | The name of the entity on which the audit occurred. This includes the following:<br /> Server objects<br /> Databases<br /> Database objects<br /> Schema objects<br /> Is nullable. Returns NULL if the entity is the Server itself or if the audit is not performed at an object level. For example, Authentication. |

| permission_bitmask | **varbinary(16)** | In some actions, this is the permissions that were grant, denied, or revoked. |

| schema_name | **sysname** | The schema context in which the action occurred. Is nullable. Returns NULL for audits occurring outside a schema. |

| sequence_group_id | **varbinary** | **Applies to**: SQL Server only (starting with 2016)<br /><br /> Unique identifier |

| sequence_number | **int** | Tracks the sequence of records within a single audit record that was too large to fit in the write buffer for audits. Is not nullable. |

| target_server_principal_name | **sysname** | Target login of action. Is nullable. Returns NULL if not applicable. |

| target_server_principal_sid | **varbinary** | SID of target login. Is nullable. Returns NULL if not applicable. |

| transaction_id | **bigint** | **Applies to**: SQL Server only (starting with 2016)<br /><br /> Unique identifier to identify multiple audit events in one transaction |

- **SQL Server**: Requires the **CONTROL SERVER** permission.

- Server admins can access audit logs of all databases on the server.

- Non server admins can only access audit logs from the current database.

- Blobs that do not meet the above criteria will be skipped (a list of skipped blobs will be displayed in the query output message), and the function will return logs only from blobs for which access is allowed.

```sql

EXEC sp_addlinkedserver

@server='myLinkedServer', -- here you can specify the name of the linked server

@srvproduct='',

1. In SQL Server Management Studio, connect to the WideWorldImporters database and open a new query window.

2. Run the following T-SQL command to enable the use of Full-Text Indexing in the database:

**Updates and fixes**

* **Database tools:**

* From now on SSDT will never disable Transparent Data Encryption (TDE) on a database. Previously since the default encryption option in a project's database settings was disabled, it would turn off encryption. With this fix encryption can be enabled but never disabled during publish.

* If the default filegroup is not PRIMARY, Import/Publish to Azure V12 would fail. Now this setting is ignored when publishing.

* Fixed an issue where when exporting a database with an object with Quoted Identifier on, export validation could fail in some instances.

* Fixed an issue where the TEXTIMAGE_ON option was incorrectly added for Hekaton table creations where it is not allowed.

ms.prod: sql

ms.date: "01/19/2017"

ms.reviewer: ""

author: Shamikg

ms.author: Shamikg

Use the Connect to SQL Azure dialog box to connect to the SQL Azure database that you want to migrate.

To access this dialog box, on the **File** menu, select **Connect to SQL Azure**. If you have previously connected, the command is **Reconnect to SQL Azure.**

description: Learn how to connect to a target instance of Azure SQL Database to migrate Access databases. SSMA obtains metadata about databases in Azure SQL Database.

ms.prod: sql

ms.custom: ""

author: "Shamikg"

ms.author: "Shamikg"

To migrate Access databases to SQL Azure, you must connect to the target instance of SQL Azure. When you connect, SSMA obtains metadata about all the databases in the instance of SQL Azure and displays database metadata in the SQL Azure Metadata Explorer. SSMA stores information about which instance of SQL Azure you are connected to, but does not store passwords.

Your connection to SQL Azure stays active until you close the project. When you reopen the project, you must reconnect to SQL Azure if you want an active connection to the server. You can work offline until you load database objects into SQL Azure and migrate data.

3. In the **Location** box, enter or select a folder for the project

SSMA creates the project file. You can now perform the next step of [adding one or more Access databases](adding-and-removing-access-database-files-accesstosql.md).