Tryangled Solutions web designing tips tricks

Often your choice of indices will make or break your database. For those who haven’t progressed this far in their database studies, an index is a sort of hash. If we issue the query SELECT * FROM users WHERE last_name = ‘Goldstein’ and last_name has no index then your DBMS must scan every row of the table and compare it to the string ‘Goldstein.’ An index is usually a B-tree (though there are other options) which speeds up this comparison considerably.

You should probably create indices for any field on which you are selecting, grouping, ordering, or joining. Obviously each index requires space proportional to the number of rows in your table, so too many indices winds up taking more memory. You also incur a performance hit on write operations, since every write now requires that the corresponding index be updated. There is a balance point which you can uncover by profiling your code. This varies from system to system and implementation to implementation.

<news.google.com>: Allows you to search 4,500 constantly updated news Web sites at once. Saves you the trip to various new sites to find out what’s going on. The new personizable version (see upper right on the page) allows you to layout the page as you like it, including personalized news searches. eg, I have it set up so that news I am interested in - India, New York Yankees, New York Jets, golf, etc - are displayed when I go to the site.

All blogs should have an RSS feed. An RSS feed will allow for your blog posts to be easily syndicated. The syndication will result in links back to your blog from RSS directories or others who display the feed. Blog entries should be available via an RSS feed. Website visitors who subscribe to the feed will receive notification when new blog posts are added. If the title is of interest, they will click through to your website. This gives subscribers an easy way to know when a blog has been updated.