Comments
1 comment
-
Official commentHi Daniel,
Thanks for reaching out to Redgate Support regarding your SQL History concern. You are correct that this is present in previous versions as it is by design, see here some details on case sensitivity from our documentation
https://documentation.red-gate.com/sp/ssms-tab-management/sql-history/searching-sql-history
Why am I not getting the results I expect?
Casing of both the words you are searching with and the query text you are searching for can have an effect on the results. To give the likeliest optimal results, compound words are broken up when searching. To do this, capital letters are treated as a word boundary.
For example, if the table CustomerOrders appears in a query, this will be broken into Customer, Orders and CustomerOrders when searching. Searching for any of these will get a result. If the CustomerOrders table was defined as Customerorders instead, searching for customer or orders will not find it.
The same word boundary logic is applied for the text being used in the search.
If you don't find what you expect to, try to change the search text slightly by lower casing it and splitting words apart.
That being said, if you would like us to add a feature to toggle case sensitivity for search results, I would recommend submitting an entry to our SQL Prompt User Voice forum so other Prompt users can vote on it and then possibly be implemented by development.
Add comment
Please sign in to leave a comment.
I have the latest version of SQL Prompt (10.16.5.15563), but this issue has occurred on previous versions as well.
I would like the option to have Case Sensitivity turned off for SQL History. As an example, I search for three different casings of SharePoint and the results are different each time. All uppercase returns nothing, all lower case returns nothing, only when spelt with the exact casing do I get the result.
My expectation is that all three searches should return the same results, as I don't want casing to influence my search results. If not, this would mean I would have to remember the exact casing of objects, which hampers quickly finding objects.
Another example, search for the term OData. When I search for the term “ODATA” I only get 1 result, where it is the exact term, but this time casing is ignored. So this is different behaviour as to the above. I'm also expecting to see the result for where the table name contains ODATA with exact case matching, but this result does not show. Only once I type out more of table name (which I don't want to do because I don't remember the table name, hence why I'm searching for it) does it find the table name.