Microsoft MDW – Message 50000

Background

As we discussed in the last couple of weeks, we are deploying Extended Events, starting to collect data and will soon start analyzing the data we collect.

 

Extended Events

Watch Live Data

Here is what things look like when we choose to “Watch Live Data“…

Image

Tabulated

  1. Database Name :- MDW
  2. Error Number :- 50000
  3. message :- insert into [space_utilization_internal]: 0 rows, 0 ms

 

Query Extended Events

Here is what things look like when we queried against the event files

Image

Textual

  1. Error Number :- 50000
  2. Message :- Insert into [databases_internal]
  3. Database :- MDW
  4. sql_text :- EXEC [sysutility_ucp_staging].sp_copy_live_table_data_into_cache_tables
  5. client_app_name :- SQLAgent – TSQL JobStep (Job 0xABCC37BF7D1A73418A87DBE3482B046A : Step 1)

 

SQL Server Agent

sysutility_get_views_data_into_cache_tables

SQL Server Agent History

Image

 

Textual


Date 4/10/2017 4:45:00 PM
Log Job History (sysutility_get_views_data_into_cache_tables)

Step ID 1
Job Name sysutility_get_views_data_into_cache_tables
Step Name Insert latest data from live tables into cache tables
Duration 00:00:00
Sql Severity 0
Sql Message ID 50000
Message
Executed as user: NT AUTHORITY\SYSTEM. sp_get_consistent_batches: 13 ms [SQLSTATE 01000] (Message 50000) Insert into [computers_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [dacs_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [volumes_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [smo_servers_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [databases_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [filegroups_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [datafiles_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [logfiles_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Discover unavailable databases: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [cpu_utilization_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Insert into [space_utilization_internal]: 0 rows, 0 ms [SQLSTATE 01000] (Message 50000) Update statistics: 43 ms [SQLSTATE 01000] (Message 50000). The step succeeded.

 

Job Steps

Image

Job Step – Insert latest data from live tables into cache tables

Image

Code

EXEC [sysutility_ucp_staging].sp_copy_live_table_data_into_cache_tables

 

Stored Procedure – [sysutility_ucp_staging].[sp_copy_live_table_data_into_cache_tables]

Image

Code

RAISERROR ('sp_get_consistent_batches: %d ms', 0, 1, @task_elapsed_ms);

RAISERROR ('Insert into [computers_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Insert into [volumes_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Insert into [smo_servers_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Insert into [datafiles_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Insert into [cpu_utilization_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Insert into [space_utilization_internal]: %d rows, %d ms', 0, 1, @row_count, @task_elapsed_ms);

RAISERROR ('Update statistics: %d ms', 0, 1, @task_elapsed_ms);

 

Conclusion

Microsoft chose to use raiserror to display formatted log messages.

Log messages in this case means number of records affected and time taken.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s