Web Strategy Blog
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.
It is often hard for those needing a website to justify the costs of design. Design is often viewed as a ‘talent’ before a learned skill, and as something that we either have or we don’t, and it naturally follows that if you ‘have it’ should be able to produce it without greart expensive.
Luke Wroblewski gave an excellent presentation at the An Event Apart 2007 conference (Chicago) that helps communicate the complexity and process of design, and the value a strong design can contribute.
Luke’s presentation focuses on the web form, which is any interface that accepts user input - common examples are login/registration, enquiry, and eCommerce checkout forms. It’s clear that many businesses depend upon their customers completing these forms to generate, maintaining and convert leads, and logically follows that the quicker and easier a form is to complete, the more likely those customers will do so.
Luke presents three simple variants of webform design to demonstrate the potential impact on revenue the design of the form can have. Each form input field has a label that tells the customer what information to put in that field. Luke’s variations placed the label above the field, and to the left of the field, either left-aligned or right-aligned. His referenced studies found that customers completing forms with right-aligned labels surprisingly did so twice as quickly as those with left-aligned labels, but that quicker still were those customers completing forms with top-aligned labels.
Clearly, big differences can be made to conversion rates by assessing the quality of your web form. Luke’s presentation is available on his blog, and goes on to discuss the consideration of required/optional fields, primary/secondary actions, contextual grouping and progressive disclosure, tabbing, the path to completion, inline validation and assistance, and feedback mechanisms.
He also provides excellent example of both good and bad web forms in a very accessible presentation that will ensure you know what to expect when commissioning the design of a web form.
I’ve just been struggling to enable full-text search on my installation of SQL Server 2005 Express Edition, and so want to share the solution.
If, like me, the ‘Use full-text indexing’ checkbox was greyed out under Database > Properties > Files, you first need to test whether Full-Text Indexing is installed or not. To do this, execute the query.
use [dbname]
select fulltextserviceproperty(’isfulltextinstalled’)
If this returns 0, you need to install Full-Text Search.
Firstly, did you install SQL Server 2005 Express Edition Advanced Series? Only the Advanced Series contains full-text. If not, you may need to reinstall.
However if so, then you just need to change the installation to include Full-Text Indexing. But if you originally installed from a download from the above link (most of you) then you’ll find that when you try to modify the installation via Control Panel > Applications / Programs, Windows prompts you for the installation file ’sqlrun_sql.msi’. This is because the download unpacked the installation files to a temporary folder which can no longer be found.
To resolve this issue, you need to download the file again from the link above, move it to a folder, and unzip (I used WinRAR). Then point Windows to the sqlrun_sql.msi file (under /setup, wherever you unzipped the download) when it prompts you for the installation file.
For additional info, see here.
For additional support setting up Full-Text Search once installed, watch this video on the topic from Micosoft, BUT I think you’ll find my new tutorial on seting up Full-Text Search in SQL Server 2005 Express much quicker and more intuitive to be honest..
« Previous Page —
Next Page »
