Connecting Tech Pros Worldwide Forums | Help | Site Map

The ISAMStats Method

ADezii's Avatar
Expert
 
Join Date: Apr 2006
Location: Philadelphia
Posts: 5,216
#1   Dec 10 '07
This week's Tip is basically geared to Power Access Users and Gurus who demand the ultimate in efficiency within their Applications. It involves an undocumented feature of Jet 4, and is a technique you can use to return a variety of pieces of information relating to Disk Reads and Writes. It is a Method of the DBEngine Object, and as such is restricted to DAO. Next week, we will discuss comparable functionality in ADO.

The ISAMStats Method is useful when you use it to compare two possible ways of doing something. Using this Method, you can retrieve information on six important statistics:
  1. Disk Reads - [0]
  2. Disk Writes - [1]
  3. Reads from Cache - [2]
  4. Reads from Read-Ahead Cache - [3]
  5. Locks placed - [4]
  6. Locks released - [5]
The basic syntax for the ISAMStats Method is as follows:
Expand|Select|Wrap|Line Numbers
  1. lngReturn = DBEngine.ISAMStats(option, [reset])
where option is a Long Integer representing one of the above listed values for each reported statistic, and reset is an optional Boolean value that, when set to True, tells Jet to reset the counter for this particular option.

I will not demonstrate this Method via a Sub-Routine Procedure, GetDAO_ISAMStats(), which accepts the name of a Query or SQL String to execute, and an Optional Argument indicating whether the code should attempt to open a Recordset or Open a Query.

For purposes of this demonstration, I've chosen to Execute a Stored Query (strQuery = qryISAMStats, blnUseRecordset = False). This Query is an Update Query, and is based on a Table consisting of 520,000 Records, 342,000 of which are updated in the process. I will also show you the Statistics generated from the Function, and hopefully, you will see how valuable this Method can be in analyzing various Query Execution Plans.
Expand|Select|Wrap|Line Numbers
  1. Public Sub GetDAO_ISAMStats(strQuery As String, Optional blnUseRecordset As Boolean)
  2. Const conDisk_Reads As Integer = 0
  3. Const conDisk_Writes As Integer = 1
  4. Const conReads_From_Cache As Integer = 2
  5. Const conReads_From_Read_Ahead_Cache As Integer = 3
  6. Const conLocks_Placed As Integer = 4
  7. Const conLocks_Released As Integer = 5
  8.  
  9. Dim dbISAM As DAO.Database, rstISAM As DAO.Recordset
  10.  
  11. Dim lngDiskReads As Long, lngDiskWrites As Long, lngReadsFromCache As Long
  12. Dim lngReadsFromReadAheadCache As Long, lngLocksPlaced As Long
  13. Dim lngLocksReleased As Long
  14.  
  15. DoCmd.Hourglass True
  16.  
  17. Set dbISAM = CurrentDb()
  18.  
  19. 'Reset all Meters
  20. Call DAO.DBEngine.ISAMStats(conDisk_Reads, True)
  21. Call DAO.DBEngine.ISAMStats(conDisk_Writes, True)
  22. Call DAO.DBEngine.ISAMStats(conReads_From_Cache, True)
  23. Call DAO.DBEngine.ISAMStats(conReads_From_Read_Ahead_Cache, True)
  24. Call DAO.DBEngine.ISAMStats(conLocks_Placed, True)
  25. Call DAO.DBEngine.ISAMStats(conLocks_Released, True)
  26.  
  27. If blnUseRecordset Then
  28.   Set rstISAM = dbISAM.OpenRecordset(strQuery, dbOpenSnapshot)
  29. Else
  30.   dbISAM.Execute strQuery
  31. End If
  32.  
  33. lngDiskReads = DAO.DBEngine.ISAMStats(conDisk_Reads)
  34. lngDiskWrites = DAO.DBEngine.ISAMStats(conDisk_Writes)
  35. lngReadsFromCache = DAO.DBEngine.ISAMStats(conReads_From_Cache)
  36. lngReadsFromReadAheadCache = DAO.DBEngine.ISAMStats(conReads_From_Read_Ahead_Cache)
  37. lngLocksPlaced = DAO.DBEngine.ISAMStats(conLocks_Placed)
  38. lngLocksReleased = DAO.DBEngine.ISAMStats(conLocks_Released)
  39.  
  40. Debug.Print "==========================================="
  41. Debug.Print "Statistics for (" & strQuery & ") - [" & IIf(blnUseRecordset, "Recordset", "Query") & "]"
  42. Debug.Print "Number of Records: " & Format$(DCount("*", "tblMain"), "#,#,#")
  43. Debug.Print "==========================================="
  44. Debug.Print "Disk Reads                     : " & Format$(lngDiskReads, "#,#,#")
  45. Debug.Print "Disk Writes                    : " & Format$(lngDiskWrites, "#,#,#")
  46. Debug.Print "Reads From Cache               : " & Format$(lngReadsFromCache, "#,#,#")
  47. Debug.Print "Reads From Read-Ahead Cache    : " & Format$(lngReadsFromReadAheadCache, "#,#,#")
  48. Debug.Print "Locks Placed                   : " & Format$(lngLocksPlaced, "#,#,#")
  49. Debug.Print "Locks Released                 : " & Format$(lngLocksReleased, "#,#,#")
  50. Debug.Print "==========================================="
  51.  
  52. If blnUseRecordset Then
  53.   rstISAM.Close
  54.   Set rstISAM = Nothing
  55. End If
  56.  
  57. DoCmd.Hourglass False
  58.  
  59. End Sub
Sub-Routine Call:
Expand|Select|Wrap|Line Numbers
  1. 'Code will Execute the Query - (blnUseRecordset = False)
  2. Call GetDAO_ISAMStats("qryISAMTest", False)
Generated Statistics:
Expand|Select|Wrap|Line Numbers
  1. ===========================================
  2. Statistics for (qryISAMTest) - [Query]
  3. Number of Records: 520,000
  4. ===========================================
  5. Disk Reads                     :    21,499
  6. Disk Writes                    :    17,862
  7. Reads From Cache               : 2,046,721
  8. Reads From Read-Ahead Cache    :    32,873
  9. Locks Placed                   :    16,514
  10. Locks Released                 :    16,256
  11. ===========================================



dima69's Avatar
Expert
 
Join Date: Sep 2006
Location: Israel
Posts: 181
#2   Dec 10 '07

re: The ISAMStats Method


Ok - so we can see the statistics on running that query.
So what is your conclusion ? Is running stored query more efficient than using DAO recordset ?
ADezii's Avatar
Expert
 
Join Date: Apr 2006
Location: Philadelphia
Posts: 5,216
#3   Dec 10 '07

re: The ISAMStats Method


Quote:

Originally Posted by dima69

Ok - so we can see the statistics on running that query.
So what is your conclusion ? Is running stored query more efficient than using DAO recordset ?

A comparative analysis between the two methodologies yielded very similar results on certain Query types. There is no conclusion, I had to leave something up to you guys to figure out (LOL). The number of Variables involved would be quite large, and it would be up to you, as the Developer, to figure out the Optimal solution for your specific set of circumstances.
Reply


Similar Microsoft Access / VBA bytes