SYMMETRICDS-488

symmetric/symmetric-assemble/src/docbook/configuration.xml

@@ -777,10 +777,10 @@ values
             An efficient way to select a subset of data from a table for an initial load is to provide an
             <literal>initial_load_select</literal> clause on <xref linkend="table_trigger_router" xrefstyle="table"/>.            
             This clause, if present, is applied as a <literal>where</literal> clause to the SQL used to select the data to be loaded.
+            The clause may use "t" as an alias for the table being loaded, if needed.
             If an <literal>initial_load_select</literal> clause is provided, data will <emphasis>not</emphasis> be passed through the 
-            configured router during initial load.  In cases where custom routing is done using a feature like <xref linkend="configuration-relational-router">Relational Routing</xref>,
-            an <literal>initial_load_select</literal> clause will always need to be provided because the router would not
-            function properly with initial load data.   
+            configured router during initial load.  In cases where routing is done using a feature like <xref linkend="configuration-subselect-router">Subselect Router</xref>,
+            an <literal>initial_load_select</literal> clause matching the subselect's criteria would be a more efficient approach.   
         </para>
         <para>
         One example of the use of an initial load select would be if you wished to only load data created more recently than the start of year 2011.  Say, for example,