0

I'm just starting to use SSMS 17.3 - and one of the main things I was looking forward to trialing was XE Profiler.

However, when you start a session (either Standard or TSQ) and add the Database Name column, it will either show as blank or NULL.

Adding a Database ID column, will show the correct DB_ID - so it can still be filtered - however, you can't see the name of which database a statement is being executed against.

3

I saw the same thing you saw. I went into the actual Properties of the Extended Event and noticed that 'collect database_name' was not checked. I checked that box and restarted the extended event session and the database_name showed up. (I had to go into each 'selected event' and check the box for 'collect database name')

Note: The XE Profiler extended events are actually under the regular Extended Events node. They are prefixed with QuickSession - That's where you change the properties. Apparently, the nodes under XE Profiler are simple shortcuts.

enter image description here

| improve this answer | |
  • 1
    I believe SeanR is referring to the new XE Profiler in SSMS 17.3 where you cannot really right click and go to the Properties. – DenisT Nov 1 '17 at 18:05
  • 1
    @DenisT - the XE Profiler extended events are actually under the regular Extended Events node. They are prefixed with QuickSession... - That's where you change the properties. – Scott Hodgin Nov 1 '17 at 18:07
  • 2
    @DenisT - I've updated my answer to hopefully make that a little more clear - thanks. – Scott Hodgin Nov 1 '17 at 18:14

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.