Eksportuj (0) Drukuj
Rozwiń wszystko
EN
Ta zawartość nie jest dostępna w wymaganym języku. Wersja w języku angielskim znajduje się tutaj.

sys.event_log

Updated: November 21, 2014

This topic is OBSOLETE. You can find the most current version in the SQL 14 Transact-SQL Reference.

ImportantImportant
This topic is not maintained. For the current version, see sys.event_log.

Returns successful Azure SQL Database database connections, as well as connection failures, deadlocks, and throttling events. You can use this information to track or troubleshoot your database activity with Azure SQL Database.

The sys.event_log view contains the following columns:

 

Column Name Data Type Description

database_name

sysname

Name of the database. If the connection fails and the user did not specify a database name, then this column is blank.

start_time

datetime2

UTC date and time of the start of the aggregation interval. For aggregated events, the time is always a multiple of 5 minutes. For example:

'2011-09-28 16:00:00'
'2011-09-28 16:05:00'
'2011-09-28 16:10:00'

end_time

datetime2

UTC date and time of the end of the aggregation interval. For aggregated events, End_time is always exactly 5 minutes later than the corresponding start_time in the same row. For events that are not aggregated, start_time and end_time equal the actual UTC date and time of the event.

event_category

nvarchar(64)

The high-level component that generated this event.

See Event Types for a list of possible values.

event_type

nvarchar(64)

The type of event.

See Event Types for a list of possible values.

event_subtype

int

The subtype of the occurring event.

See Event Types for a list of possible values.

event_subtype_desc

nvarchar(64)

The description of the event subtype.

See Event Types for a list of possible values.

severity

int

The severity of the error. Possible values are:

0 = Information
1 = Warning
2 = Error

event_count

int

The number of times that this event occurred for the specified database within the time interval specified (start_time and end_time).

description

nvarchar(max)

A detailed description of the event.

See Event Types for a list of possible values.

additional_data

XML

For Deadlock events, this column contains the deadlock graph. This column is NULL for other event types.

The events recorded by each row in this view are identified by a category (event_category), event type (event_type), and a subtype (event_subtype). The following table lists the types of events that are collected in this view.

For events in the connectivity category, summary information is available in the sys.database_connection_stats view.

noteNote
This view does not include all possible Azure SQL Database database events that can occur, only those listed here. Additional categories, event types, and subtypes may be added in future releases of Azure SQL Database.

 

event_category event_type event_subtype event_subtype_desc severity description

connectivity

connection_successful

0

connection_successful

0

Connected successfully to database.

connectivity

connection_failed

0

invalid_login_name

2

Login name is not valid in this version of SQL Server.

connectivity

connection_failed

1

windows_auth_not_supported

2

Windows logins are not supported in this version of SQL Server.

connectivity

connection_failed

2

attach_db_not_supported

2

User requested to attach a database file which is not supported.

connectivity

connection_failed

3

change_password_not_supported

2

User requested to change the password of the user logging in which is not supported.

connectivity

connection_failed

4

login_failed_for_user

2

Login failed for user.

connectivity

connection_failed

5

login_disabled

2

The login was disabled.

connectivity

connection_failed

6

failed_to_open_db

2

Database could not be opened. May be caused because database does not exist or lack of authentication to open the database.

connectivity

connection_failed

7

blocked_by_firewall

2

Client IP address is not allowed to access the server.

connectivity

connection_failed

8

client_close

2

Client may have timed out when establishing connection. Try increasing the connection timeout.

connectivity

connection_failed

9

reconfiguration

2

Connection failed because the database was going through a reconfiguration at the time.

connectivity

connection_terminated

0

idle_connection_timeout

2

Connection has been idle for longer than system defined threshold.

connectivity

throttling

<reason code>

reason_code

2

Request is throttled.  Throttling reason code: <reason code>. For more information, see Engine Throttling.

connectivity

throttling_long_transaction

40549

long_transaction

2

Session is terminated because you have a long-running transaction. Try shortening your transaction. For more information, see Resource Limits.

connectivity

throttling_long_transaction

40550

excessive_lock_usage

2

The session has been terminated because it has acquired too many locks. Try reading or modifying fewer rows in a single transaction. For more information, see Resource Limits.

connectivity

throttling_long_transaction

40551

excessive_tempdb_usage

2

The session has been terminated because of excessive TEMPDB usage. Try modifying your query to reduce the temporary table space usage. For more information, see Resource Limits.

connectivity

throttling_long_transaction

40552

excessive_log_space_usage

2

The session has been terminated because of excessive transaction log space usage. Try modifying fewer rows in a single transaction. For more information, see Resource Limits.

connectivity

throttling_long_transaction

40553

excessive_memory_usage

2

The session has been terminated because of excessive memory usage. Try modifying your query to process fewer rows. For more information, see Resource Limits.

engine

deadlock

0

deadlock

2

Deadlock occurred.

Users with permission to access the master database have read-only access to this view.

The following query returns all events that occurred between noon on 9/25/2011 and noon on 9/28/2011 (UTC). By default, query results are sorted by start_time (ascending order).

select * from sys.event_log where start_time>='2011-09-25:12:00:00' and end_time<='2011-09-28 12:00:00'

The following query returns all deadlock events for database Database1.

select * from sys.event_log where event_type='deadlock' and database_name='Database1'

The following query returns hard throttling on SQL Worker Threads events that occurred between 10:00 and 11:00 on 9/25/2011 (UTC).

select * from sys.event_log where event_type='throttling' and event_subtype=4194307 and start_time>='2011-09-25 10:00:00' and end_time<='2011-09-25 11:00:00'

Event Aggregation

Event information for this view is collected and aggregated within 5-minute intervals. The event_count column represents the number of times a particular event_type and event_subtype occurred for a specific database within a given time interval.

noteNote
Some events, such as deadlocks, are not aggregated. For these events, event_count will be 1 and start_time and end_time will equal the actual UTC date and time when the event occurred.

For example, if a user fails to connect to database Database1, because of an invalid login name, seven times between 11:00 and 11:05 on 2/5/2012 (UTC), this information is available in a single row in this view:

 

database_name start_time end_time event_category event_type event_subtype event_subtype_desc severity event_count description additional_data

Database1

2012-02-05 11:00:00

2012-02-05 11:05:00

connectivity

connection_failed

4

login_failed_for_user

2

7

Login failed for user.

NULL

Interval start_time and end_time

An event is included in an aggregation interval when the event occurs on or afterstart_time and beforeend_time for that interval. For example, an event occurring exactly at 2012-10-30 19:25:00.0000000 would be included only in the second interval shown below:


start_time                    end_time
2012-10-30 19:20:00.0000000   2012-10-30 19:25:00.0000000
2012-10-30 19:25:00.0000000   2012-10-30 19:30:00.0000000

Data Updates

Data in this view is accumulated over time. Typically, the data is accumulated within an hour of the start of the aggregation interval, but it may take up to a maximum of 24 hours for all the data to appear in the view. During that time, the information within a single row may be updated periodically.

Data Retention

The data in this view is retained for a maximum of 30 days, or possibly less depending on the number of databases in the logical server and the number of unique events each database generates. To retain this information for a longer period, copy the data to a separate database. After you make an initial copy of the view, the rows in the view may be updated as data is accumulated. To keep your copy of the data up-to-date, periodically do a table scan of the rows to look for an increase in the event count of existing rows and to identify new rows (you can identify unique rows by using the start and end times), then update your copy of the data with these changes.

Errors Not Included

This view may not include all connection and error information:

  • This view does not include all Azure SQL Database database errors that could occur, only those specified in Event Types in this topic.

  • If there is a computer failure within the Azure SQL Database datacenter, a small amount of data for your logical server may be missing from the event table.

  • If an IP address has been blocked through DoSGuard, connection attempt events from that IP address cannot be collected and will not appear in this view.

Pokaż:
© 2014 Microsoft