Used to be a Remedy admin a few years ago and I realize many things have changed for the better with the Remedy product. Now, managing the process side of Remedy instead of the developement and have a few questions for the Remedy/SQL 2000 experts. In the past we have always had a function in our customer built Remedy help desk form called keyword search. It would search all the tickets in the system for the keywords entered. Something like this - "%keyword%" LIKE "%" + 'Problem Description' + "%". The issue is we want to use this type of search for a new knowledge base we are building and are being told by our devs that it will hamper our system performance to use search wrapped in %. The search will reference a charter field limited to 245 characters. We ran our system for around 2 years with about 250,000 records in it with no issues previously, however with the new devs and changes taking place are starting to see some performance issues.
So my question is that can anyone shed some light on using or not using search on your DB wrapped in %. The claim is that the field is not index and the search result in a full SQL table scan - I realize this but can't help but think how we ran so long doing it this way for so long. At this time we are getting a lot of grief about creating the knowledge base in this way. Any comments on this ? Thank in advance.
So my question is that can anyone shed some light on using or not using search on your DB wrapped in %. The claim is that the field is not index and the search result in a full SQL table scan - I realize this but can't help but think how we ran so long doing it this way for so long. At this time we are getting a lot of grief about creating the knowledge base in this way. Any comments on this ? Thank in advance.