- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2015 09:22 AM
I'm trying to combine the sysevent and sys_user tables in a database view to capture login-related events.
I've been struggling to get it working.
Every time, I want to test it - it crashes. I have no idea why.
Thanks,
D.
Solved! Go to Solution.
- Labels:
-
Instance Configuration
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2015 10:49 AM
Can you please check your Table Rotations module? You should see sysevent in the Table Rotations. Database views can not be created on Rotated tables and this is most likely the cause of the problem (Database Views - ServiceNow Wiki). Additionally, Database Views can not include Extended tables either.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2015 01:15 PM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2015 01:16 PM
Like Travis, long posts are being blocked. It's an update set that logs each login on a table that has a reference to the user, for reporting purposes.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-09-2015 11:09 PM
I remember looking at this recently. Now, I know why you had to build a separate table to hold the login data.
D.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2015 11:52 AM
I can see why ServiceNow didn't want to put a reference field on their sysevent table, but dot-walking is so important! For example, here's an Explore Analytics map report of logins... gives you a whole new world of information.