There are a real plethora of eCommerce solutions out there now, making it difficult to isolate which solution is best for you. Some solutions are free and open-source, some licensed or bought off the shelf, and others custom-built - each has it’s advantages and disadvantages. This post is an outline of what your decision-making process with your IT consultant should look like.
- Will you be marketing your products to the search engines? If so, you need, at a minimum, a solution with 301 Redirect Management, keyword-rich URLs, and management facilities for title and meta-tags. This will rule out a sleuth of options.
- What is your estimated annual turnover, average transaction value, and average unit price? Payment gateways (i.e. PayPal, Google Checkout, Protx, ChronoPay, etc.) differ in their charges, and you should choose to minimise your costs.
More >>
For the life of me, I couldn’t figure out why I didn’t get different results, using SQL Server 2005, for a simple Full-Text Search query and a Full-Text Search query using the FORMSOF and INFLECTIONAL keywords.
What I stumbled across eventually was that when creating and configuring my SQL Full-Text Indexes, I had left the language parameter as the default selection. When I changed this to English, voila!, my FORMSOF (INFLECTIONAL, @query) queries started to produces fantastic search results!
Also, an example query showing how to parameterize the the search term, and how to rank your results:
@query
varchar (100)
SET @query = ‘FORMSOF (INFLECTIONAL, ‘ + @query + ‘)’
SELECT FT.rank, P.id, P.title
FROM Products P
INNER JOIN CONTAINSTABLE (Products, *, @query) AS FT ON P.id = FT.[key]
If you’ve any questions, I’ll do my best to help. Also, if you’re just starting with Full-Text, check out my posts on installing Full-Text Search on SQL Server 2005 and how to setup and configure SQL Server 2005 Express Full-Text Search the easy way.
I recently had to setup a search facility on a website driven by SQL Server 2005 Express. My natural choice was SQL Server’s Full-Text Search feature, but setup was not entirely intuitive, and the web was full of misinformation. I’ve put together a tutorial to save you time.
If you’re not sure if your have Full-Text installed, read my post on installing SQL Server 2005 Express Full-Text Search.
Once, Full-Text is installed, you need to create your index:
CREATE FULLTEXT CATALOG MyFullTextCatalog
Managing your index is then actually very simple:
- Browse to the tables of your database, right click and select ‘Design’
- In the main window, right click and select ‘Fulltext Index…’
If you see the message, ‘You need to define one or more full-text compatible indexes on the table to create a full-text index’ and the ‘Add’ button is greyed out, it’s because you don’t have a column the database can use to uniquely identify each row. Make sure you have a primary key, and if you’ve no success, start your troubleshooting with this video - it discusses unique indexes about 1/3 of the way through.
- Otherwise, click ‘Add’, and you have a new index.
- To configure the columns in the index, click the ‘…’ button next to ‘Columns’
- For each column, select the column, and select the appropriate language
To understand why the language parameter is important, see my post on use of the FORMSOF and INFLECTIONAL keywords in SQL Full-Text Search
It’s that easy! Any questions, let me know and I’ll do my best to help.
