Since the question is a bit unclear to me, I'm assuming that the information string acts as a key-sort-of-thing for additional information (like a title for an article), and there is no true GET search requirement.
If this is the case, if allowed to modify the database structure, I would use some kind of surrogate key instead (like a numeric identifier), using the title-thingy as a slug).
In this case, your when generating links in your website, you get both the id and slug for the target, and create an url of it in the format http://example.com/[id]/[slug]/
, for example http://example.com/213/omg-lol-the-cat-jumped/
.
When processing the request in your server, you are only interested in the id ("213"), and the slug ("omg-lol-the-cat-jumped") is just for the human user to give a sneak-peek of the title, and doesn't affect the search result. You provide the page that matches the id, not the slug. This way, your searching is efficient (no SQL LIKE-matching), and less error prone (SQL injections from malformatted slugs).
As for the (possible?) question about how to convert a string into a slug, there are many approaches to that. I would simply remove all non-alphanumeric characters, and combine the alphanumeric chunks with dashes or underscores. You probably want to cut the string length to 20-ish characters.