Reputation
503
Top tag
Next privilege 1,000 Rep.
See votes, expandable usercard
Badges
1 4 16
Impact
~30k people reached

  • 0 posts edited
  • 0 helpful flags
  • 80 votes cast
Aug
21
comment Unable to Watch Live Data on Extended Events Session
Good idea. I can duplicate it with both SQL and Windows logins. It's all about the default database assigned to the login.
Aug
21
comment Unable to Watch Live Data on Extended Events Session
I am using a Windows login that is mapped to public and sysadmin.
Aug
21
comment Unable to Watch Live Data on Extended Events Session
@AaronBertrand Yes, I agree! SSMS should know how to connect to the event session regardless of my default database. I linked a Microsoft Connect item in my question, should anyone want to vote or comment on it.
Aug
20
comment Unable to Watch Live Data on Extended Events Session
Yes, thank you. I have 2 days until I can accept my answer.
Aug
20
revised Unable to Watch Live Data on Extended Events Session
added 70 characters in body
Aug
20
comment Unable to Watch Live Data on Extended Events Session
I found the answer. My login's default database was set to the one I usually use instead of master. Setting my default database back to master resolved the error.
Aug
20
answered Unable to Watch Live Data on Extended Events Session
Aug
20
asked Unable to Watch Live Data on Extended Events Session
Jun
12
revised SQL Server varbinary column modifying inserted data
added 453 characters in body
Jun
12
answered SQL Server varbinary column modifying inserted data
Jun
12
accepted Slow Performance Inserting Few Rows Into Huge Table
Jun
12
awarded  Famous Question
Jan
19
accepted Why are timestamps not always increasing with concurrent inserts?
Jan
19
awarded  Popular Question
Dec
8
awarded  Popular Question
Oct
15
awarded  Popular Question
Sep
8
awarded  Notable Question
Jul
2
awarded  Curious
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
@MaxVernon - Actually, this could be a problem for us even in READ COMMITTED isolation. If the second transaction finishes before the first with its higher timestamp values, then our cache will retrieve it. Unfortunately, since its maximum known timestamp is now higher than all of the first transaction's records, our caching code will never retrieve any of them.
Nov
25
comment Why are timestamps not always increasing with concurrent inserts?
@Kin - Martin Smith is correct, the function is essentially a tally table.