And damnit, got to remember the joys of SQL Server versions. Started poking at full text indexes, what should be the solution to the issues with search taking ages, only to get the reminder from the system that the version I have for testing doesn't support them. Which also means I have to make sure the new host I'm looking at does support them.

So suck is abundant today. Poking at the core Tag based archive queries instead, but while I do that have some references on just what full text indexing can do.

My favorite part:
Comparing LIKE to Full-Text Search

In contrast to full-text search, the LIKE Transact-SQL predicate works on character patterns only. Also, you cannot use the LIKE predicate to query formatted binary data. Furthermore, a LIKE query against a large amount of unstructured text data is much slower than an equivalent full-text query against the same data. A LIKE query against millions of rows of text data can take minutes to return; whereas a full-text query can take only seconds or less against the same data, depending on the number of rows that are returned.

As you might guess I'm using LIKE now, and it's entirely why things take so long to search. But it's also the way to do text matches that's always available and doesn't take up any space. With me not even having enough space on this server to do regular maintenance without SQL acrobatics being involved.

Anyway, working on Tagging instead. Going with the simple 'One Tag Archive' approach instead of something I can fuck with for months. Once I'm done with that it'll be time to start working on some of the outward facing pages, so we'll see how that goes and revisit full text indexing later.