James

Age: 37

DBA/developer. Mostly SQL Server. Ex-sysadmin.

4h
awarded Good Answer
5h
awarded Mortarboard
10h
revised NOLOCK hint changes order of records returned
Uploaded a more illustrative image (shows breaks in apparent sort order for both sets)
11h
revised NOLOCK hint changes order of records returned
deleted 191 characters in body
12h
awarded Nice Answer
16h
revised NOLOCK hint changes order of records returned
added 23 characters in body
17h
revised NOLOCK hint changes order of records returned
added 186 characters in body
18h
revised NOLOCK hint changes order of records returned
added 159 characters in body
18h
revised NOLOCK hint changes order of records returned
uploaded less blurry image
18h
answered NOLOCK hint changes order of records returned
Aug
29
revised Azure: Many Failed Login Attempts Logged
added 19 characters in body
Aug
29
answered Azure: Many Failed Login Attempts Logged
Aug
27
comment How is an idle SQL Server connection causing blocking?
You might find dumping the output of sp_WhoisActive to a table every 15 seconds or so more helpful than the blocked process report. @get_locks=1 will give you an XML document showing which locks were acquired and being waited for, which might give a clue about what statements were run in the idle session. @get_additional_info=1 will also give you the isolation level.
Aug
25
comment incremental update in HBase using sqoop
Is this not answered in the Sqoop documentation here?
Aug
25
awarded Caucus
Aug
24
awarded Autobiographer
Aug
24
comment SQL DatabaseMail smtp error 5.7.57 at one site, email works at another with the same details
Yes I believe you'll need to add @port = 587 per the information here. If that doesn't work, do you get any further details in the Database Mail log if you enable verbose logging?
Aug
24
awarded Supporter
Aug
24
awarded Autobiographer
Aug
23
comment Stuck in "query end" status every 5 minutes
You may want to have a look at this similar question. Your situation might be somewhat different, but the question has the sorts of details (and links to more) that you'll need to figure out InnoDB write stall problems.
1 2 3 4 5