PI can only search using visible portion of the SQL statement but not from any other part from deeper into the batch text.  (4377502)

The user displays the full batch text from the SQL PI SQL Statement Dashboard for a particular statement, then selects a random string which is not visible on the overview and uses it to search back from the PI./SQL Statement list and throw no results.

PI can only search using visible portion of the SQL statement but not from any other part from deeper into the batch text. 

This is done because the search box is a WCF function that is designed to search only the contents of the box, not the entire SQL text of every field for every SQL statement.

The UI limits the size to 128 characters for performance reasons, with the first middle three characters in the SQL replaced with a ... to fit the space. By default the SQL text is up to 16400 characters long, with some users setting sql text sizes into the millions (which isn't recommended). Adding a search through ALL SQL text could have a significant performance impact. FGSS-I-67 was already added to increase the size of the field from 128 characters.

WORKAROUND

None

STATUS

Enhancement Request FOGGENERAL-I-307 was logged to add a search through all of the SQL text for all of the Top SQL queries. This will be reviewed by Product Management for inclusion in a future release of SQL PI.