Comments on: A better way to index text datahttp://itknowledgeexchange.techtarget.com/sql-server/a-better-way-to-index-text-data/
Sun, 22 Mar 2015 23:21:07 +0000hourly1By: Mrdennyhttp://itknowledgeexchange.techtarget.com/sql-server/a-better-way-to-index-text-data/#comment-78
Thu, 31 Jul 2008 02:54:17 +0000http://itknowledgeexchange.techtarget.com/sql-server/a-better-way-to-index-text-data/#comment-78If there was a requirement for breaking the data out, that could be an excellent solution. If your system requirements are for a single column where the email address is a username for example, then breaking the column apart may not be the best option in that case.

Thanks for showing an additional method which can be used.

If anyone else has other options please post them.

]]>By: DMUNSEENhttp://itknowledgeexchange.techtarget.com/sql-server/a-better-way-to-index-text-data/#comment-75
Wed, 30 Jul 2008 07:39:22 +0000http://itknowledgeexchange.techtarget.com/sql-server/a-better-way-to-index-text-data/#comment-75After thinking about this for a while, I suspect that for email addresses there is probably a more complete solution (where you can also use other types of matching than just equality through a hash column) that is also scalable:
Just (partly) normalize all the different parts of the email address (e.g. create one or more tables like email_prefix,email_domain or email_extension). Fora large set of email addresses this would give you a considerable size reduction since you would store each part of the email address only once, and you do not need to store the email address @ and dot character.
Since this means you can now index the individual emailaddress parts more easilty It would also make partial matches to email address(parts) possible.

my suggestion is not practical for small sets since it would actually increase not only the total size of the data, but it would also make some matching queries needlessly complex.