What should be considered when NOLOCK hint is used

IntroductionWith SQL Server the NOLOCK hint is very tempting especially with SELECT statements where at least one of the tables is frequently updated. Using the NOLOCK removes all queueing problems and the SELECT statement runs smoothly, but not without side effetcs. Why do we need a hint at allFirst question might be that why do we need to add this hint to get the statement running without