average porn star herbal penis size size

just another regularban.info web blog

MEMBERS:

Efficient SQL Databases

Don't be fooled by seeming simplicity. A lot of developers get comfortable with a certain way of designing a database for their web applications that they miss out on techniques they should rather employ to make things run faster and more efficiently. A lot of developers don't bear in mnd that the small site they are creating now might grow into something incredibly large and complex, and the database they designed has become bloated and doesn't scale well to meet the demands of the increased traffic.

This article hopes to provide web developers with a few techniques to help make their database and queries faster and more efficient.

1. Avoid Character Types

When you are designing a database, it is so easy to set all data types to the VARCHAR type as it can then contain any data you want; numbers or text. But character data is amongst the most inefficient data type you can get. If a field is only going to contain numbers, then make it one of the appropriate types (INT, DOUBLE, etc).

Also, wherever possible in your web development code, try to use numeric data types as opposed to characters. One of the most common things a script has to store are flags like whether someone answered yes or no to a question, etc. You could of course store it as 'Y' or 'N' but why not store it as 0 and 1?

The reason this makes a difference is when you have a database, for example, with over 500 000 entries, and are running a SELECT on that field, comparisons are processed a lot faster for numeric data types than character types. Also, if you need to return data to the calling script, numeric data is less memory intensive than character data. In addition, your web development language (PHP, ASP, etc) would also be able to process and perform functions on numeric data better than character data.

I am not trying to convince you never to use character data types. Sometimes it is a necessity, but if you can find ways to reduce the amount of character data processed by your SQL database, the better your server will cope.

2. Normalization

Normalizing a database is really quite a complex process. It is a process that describes a way to design a database structure to avoid repetition of data in your database and can lead to significant performance benefits if employed correctly. However, the entire process of normalisation is a bit beyond the scope of this article as it can fill books on its own, but any developer designing a database should seriously consider becoming knowledgable about normalisation and employing it in their own designs.

For a good tutorial on this process: http://www.keithjbrown.co.uk/vworks/mysql/mysql_p7.php

3. DateTime vs Timestamp fields

This actually relates to 1. a bit. The big difference to bear in mind here is that a field of type DATETIME is actually stored as a series of characters. A field of type TIMESTAMP is actually stored as an integer. So therefore, a more efficient way of storing dates is using the timestamp method. The timestamp has its drawbacks however. For one, you cannot store a date early than 1 January, 1970. Also, timestamps in your script will need recalculating to get to the character format. Because of this recalculation, it may not be better to store as timestamp. It really is a case of testing which format works better for your needs.

4. Use LIMIT where possible

In your queries, if you are doing a SELECT to a database and you only expect a certain number of results, using the LIMIT statement can speed your query up incredibly.

For example, if you have a table of users and you need to run a query to search for one users record, you can use a query like:

SELECT user_name FROM users WHERE user_id = 453;

This query is perfectly valid and will return the right result. But you also know there will only be ONE result. The query above will search the database, find what you want, but then still continue searching after that. It would run a lot faster if you could tell the query that once it has found what you are looking for to stop searching. LIMIT can do this, as this query shows:

SELECT user_name FROM users WHERE user_id = 453 LIMIT 1;

Imagine this scenario. You have a table called logins, that records every login from a user. It currently contains over 2 000 000 records, and you want to find the first time a user logged in. Now bear in mind that because this table inserts data over time, it is already sorted for by date. You could do the following query:

SELECT MIN(login_date) FROM logins WHERE user_id = 4876;

This will return the record you want, but SQL will now have to get all dates for that user, sort them and then return the lowest value to you. Our table is already date sorted simply because of the way it records data for us. So using LIMIT can be more effective:

SELECT login_date FROM logins WHERE user_id = 4876 LIMIT 1;

Because it is sorted, the first one will always be a users first login.

5. Avoid using LIKE

If you have tried to employ 1. above, then hopefully you will be in a scenario where you do not need to use LIKE all that much. LIKE is one of the most inefficient ways of searching a table. LIKE performs a text comparison search in a field and with no wildcards is as efficient as a direct comparison; i.e. WHERE name = 'Jane' is equivalent to WHERE name LIKE 'Jane'. It is when you start introducing the wildcard characters like '%' that things get really hairy.

If you do have to use LIKE, then at least try and make efficient use of the wildcards. These are '_' (underscore) and '%'. Let me explain all this with a real world example.

In a project I was involved in, we had a SQL database storing logs generated automatically from a mail server. Unfortunately, the mail server pretty much just dumped a very long string of text data into a field that contained the data we wanted. A script had to be written to find all logs that referred to a login by a user into the POP server. The only way we could do this was to search every record for a string in the msg field that had the text "User logged in" in it. The first query developed was something like this:

SELECT msg FROM logs WHERE msg LIKE '%User logged in%';

This query took on average of about 35 minutes to process. Obviously not an ideal situation. The way the LIKE worked here was that it had to parse through every single portion of each and every record in the msg field looking for text that matched "User logged in" anywhere in the text. We were able to determine eventually that the text "User logged in" occured at the end of that text in the msg field and so we altered the query:

SELECT msg FROM logs WHERE msg LIKE '%User logged in';

The '%' at the end was removed as we do not want to worry about text after because there is none. The query now only compares text to our string in the msg field at the end of the field and no longer parses through the entire piece of text stored in msg. The query now ran in under 2 minutes. (This was actually still too long, but how we optimised from there is a little beyond the scope of this article.)

Hopefully with all these elements put into practice on your next web development project, you can have a database that runs quickly, efficiently, uses as little resources as possible and wont grind to a halt when the load suddenly increases.

Gareth McCumskey works as the Systems Developer for Synaq, a South African based Linux support and services provider. He has been involved in web development for over nine years and programming since he was 13.

 


Principles Of Good Web Content Development

Good content is a key factor that determines the success of any website. It is therefore very important that a website should host good and appropriate content in it's pages. There are various factors such as uniqueness, freshness and keyword usage that determine the effectiveness and appropriateness of web content.

Uniqueness of content ensures that the content is found only in your website. This should be specifically tailor-made for your website. Take your own time to prepare this in a most appealing manner. The time and effort you are putting in developing the content will give you good returns in the long run.

A fresh content tries to deal with a subject in a more interesting way. It helps to retain your visitors in your site and prompts them to spend more time there. The more time a visitor spent in your site, the more are the chances to generate a sale from your website.

Keywords are very important as far as any content development process is concerned. Search engines find more value in keywords. This is the major difference web content have with printed content. When you are writing for a website you are not only targeting visitors but also the Search Engines. Keywords lure the search engines to the web pages your website contains. The main challenge in good development is to make sure that you are not loosing quality and purpose of the content while developing your content with keywords. Identifying the keywords for your site should be done carefully. Research on potential keywords for your site with some keyword analysis tools is helpful. Traffic data analysis is also helpful in determining the selection of keywords for your Web Pages.

Read Building Text Link Advertisements

Gijo George

Visit Perfect Gifts. Fetch a gift that is truly unique!

 


How Good Is Your Website Building Company?

Hello

I am a person who decided 3 years ago that I wanted to create or build my own websites.

The company I use to assist me not only has ALL the tools and All the advice and ALL the assistance and can prove ALL that it says and is SO cheap to purchase, just today it surprised me AGAIN.

It appears that they had a little setback with one of the tools they provide. This tool is a major tool for all of us who are building websites.

Did they deny the problem? No.
Did they try to pass the blame onto someone else? No.
Did they try to hide from a lot of angry customers? Again, no.

Here is what they did.
They sent an email out to everyone, yes that's right everyone telling us that there was a problem AND APOLOGIZING PROFUSELY!

In addition they compensated us for the inconvenience by adding credits to the tool that was affected.

They kept in contact with us all through a forum which was very easy to locate and use.

They received many, many words of encouragement from a lot of website builders basically saying - thanks for the extra credits and no problem with the glitch.

Then the company advised after many testings that the problems were all fixed and we were good to go.

NOW IS THIS THE TYPE OF SERVICE YOUR COMPANY PROVIDES?

I'm reasonably confident that a lot of people are paying a lot of money for a product which does NOT do all that this particular company does. Question is why do so many people stay with that type of website building company?

If you would like to compare your current website building company head to http://www.Airplane-and-Aircraft.com and head down to the "Holding Pattern" on the homepage. You will find a link there to what I am 95% confident is the best website building company around. As I said before they just continue to prove it over and over again. Even the price for all the tools, service and assistance is amazingly cheap.

All the best.
Geoff

I have heard many times that many website building companies charge up to thousands of dollars to assist people build a website. Some will only charge you a nominal fee (initially) and then charge you more and more for the extras needed.

Not the company that I build with. They're amazing AND I CAN PROVE IT.

 


Pages 
* About

Archives
    * February 2008
    * January 2008

Categories:
* Uncategorized

Last Updated:

regularban.info is proudly powered by WordPress MU running on  regularban.info.
Create a new blog and join in the fun!
Entries (RSS) and Comments (RSS).


  blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor blackhatseotoolsmentor