OpenData - Revision history

Lsilverman: /* Query Performance and Volume */

2023-05-10T21:28:40Z

Query Performance and Volume

Lsilverman at 21:27, 10 May 2023

2023-05-10T21:27:48Z

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:17:09Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:16:54Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:16:41Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:14:58Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:14:28Z

update (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:09:25Z

update (by SublimeText.Mediawiker)

Lsilverman: formatting (by SublimeText.Mediawiker)

2023-04-12T18:08:11Z

formatting (by SublimeText.Mediawiker)

Lsilverman: update (by SublimeText.Mediawiker)

2023-04-12T18:07:58Z

update (by SublimeText.Mediawiker)

@@ Line 192: / Line 192: @@
 Here are some performance tips:
-* Try not to use SELECT * (unless you're just exploring, initially) -- try to only fetch the columns you require.
+* Try not to use <code>SELECT *</code> (unless you're just exploring, initially). Fetch only the columns you require.
 * Please be conscious of how frequently you schedule executions.
 * Try to use precise WHERE clauses to return just the data you require, and not pull back the entire history of transactions. Over time, as your database grows with use, you may find queries getting slower and slower with the accumulation of TrackAbout data.

@@ Line 188: / Line 188: @@
 The data views are read-only by design. You cannot write to this data. Writing is not a planned feature.
-==Query Volume==
+==Query Performance and Volume==
-It is our expectation that you will not abuse the database by re-running very large or expensive queries frequently. The database platform has finite resources, and abuse will impact other users. TrackAbout will be monitoring usage and will throttle or slow down users who abuse their databases.
+It is our expectation that you will not abuse the database by re-running very large or expensive queries frequently. The database platform has finite resources, and abuse will impact other users. TrackAbout will be monitoring usage and will throttle, slow down or even block users who abuse the system.
 Local data caching (copying data to a local database or temporary table) is recommended if you need to re-query the same data repeatedly.

@@ Line 133: / Line 133: @@
 </pre>
-Above, the line <code>cr8.centralus1-a.control.database.windows.net. 0 IN A 13.89.169.20</code> contains the final lookup which resulted in a valid IP address. This is a positive (good) test result.
+Above, the line <code>cr8.centralus1-a.control.database.windows.net. 0 IN A 13.89.169.20</code> contains the final lookup which resulted in a valid IP address (13.89.169.20). This is a positive (good) test result.
 === Testing TCP/IP Connectivity ===

@@ Line 133: / Line 133: @@
 </pre>
-Above, the line <code>cr8.centralus1-a.control.database.windows.net. 0 IN A 13.89.169.20</code> contains the final lookup which resulted in a valid IP address.
+Above, the line <code>cr8.centralus1-a.control.database.windows.net. 0 IN A 13.89.169.20</code> contains the final lookup which resulted in a valid IP address. This is a positive (good) test result.
 === Testing TCP/IP Connectivity ===

@@ Line 132: / Line 132: @@
 ;; MSG SIZE  rcvd: 502
 </pre>
 === Testing TCP/IP Connectivity ===

@@ Line 167: / Line 167: @@
 Connection to ta-proddb-ceus.database.windows.net (13.89.169.20) 1433 port [tcp/ms-sql-s] succeeded!
 </pre>
 ==Try a Query==

@@ Line 71: / Line 71: @@
 == Troubleshooting Connectivity ==
 If you're having trouble connecting, follow these steps to eliminate the most common causes.
 === Testing DNS Resolution ===
-Every address on the internet like our database's address of <code>ta-proddb-ceus.database.windows.net</code> has to be turned into an IP Address by your computer. In some environments, this so-called "DNS resolution" might not be working right due to a network misconfiguration or even local network security policy.
+Every address on the internet like our database's address of <code>ta-proddb-ceus.database.windows.net</code> has to be turned into an IP Address by your computer. In some environments, this so-called "DNS resolution" might not be working due to a network misconfiguration or even local network security policy blocking access.
-Here are two ways to test.
+;Test DNS using nslookup on Windows
 Open a PowerShell command prompt (powershell.exe) and execute the following command:
@@ Line 100: / Line 100: @@
 </syntaxhighlight>
-; Using dig
+We're looking for a valid IP address under "Non-authoritative answer:".
 If you're on Linux or a Mac, you will need to use the "dig" command. If it's not installed, check your package manager for <code>bind-utils</code>.
 <console>
@@ Line 107: / Line 109: @@
 </console>
-<syntaxhighlight lang="bash">
+<pre>
 ; <<>> DiG 9.18.1-1ubuntu1.3-Ubuntu <<>> ta-proddb-ceus.database.windows.net
 ;; global options: +cmd
@@ Line 129: / Line 131: @@
 ;; WHEN: Wed Apr 12 13:05:03 CDT 2023
 ;; MSG SIZE  rcvd: 502
-</syntaxhighlight>
+</pre>
 === Testing TCP/IP Connectivity ===
-Next we're going to test whether your computer can find a route on the network to our database server.
+Once we've verified name resolution is working, we move on to testing end-to-end connectivity.
-In the same Powershell command prompt, run this command:
+;On Windows
 <console>
@@ Line 152: / Line 157: @@
 Anything else indicates a failure to reach the remote server. You should contact your local IT network support for help.
 ==Try a Query==

@@ Line 105: / Line 105: @@
 <console>
-$ dig ta-proddb-ceus.database.windows.net
+dig ta-proddb-ceus.database.windows.net
 </console>