Skip to main content

Search engine results are almost always wrong!

This is the mail which I sent to my team mates / group of friends in Verizon on 9th Feb 2006. I thought let me post it here as well.


Does search engines lie on the number of results shown for a search string?

I tried searching for the word "vadivel.blogspot" in Google. It said there are 178 results found. But actually they are able to display only 23 results. The funny part is ... at the end of the page there was this block of text.

"In order to show you the most relevant results, we have omitted some entries very similar to the 23 already displayed. If you like, you can repeat the search with the omitted results included."


So now I searched again including the duplicates as well .. still it is able to list only 168 results :)

After this, I searched the same search string in Yahoo it said 164 results are there. But on clicking 2nd page ... the numbers changed to 280!! very strange. Still they where listing 129 records only.

So to my knowledge the numbers which "Search engines" show is almost always wrong. Don't get misleaded by that number.

I tried the same search query on MSN and it returned only 23 results. No disclaimers found whatsoever. All 23 entries were unique and there were no duplicates. So to me MSN is the best search engine (atleast for this search string :)).

Hmm one another reason why we need to stick with Microsoft products.

Comments

Srini said…
Interesting :)

Now, how about the time they display for these search string. G,Y and M takes 0.51,0.22 and 0.25 seconds respectively. Any possibility for lies here also?
Vadivel said…
Welcome to my blogspace srini.

That's an interesting question you have asked. I don't think I have any substantial facts before me to talk in favor or against it :)

Popular posts from this blog

Registry manipulation from SQL

Registry Manupulation from SQL Server is pretty easy. There are 4 extended stored procedure in SQL Server 2000 for the purpose of manupulating the server registry. They are: 1) xp_regwrite 2) xp_regread 3) xp_regdeletekey 4) xp_regdeletevalue Let us see each one of them in detail! About xp_regwrite This extended stored procedure helps us to create data item in the (server’s) registry and we could also create a new key. Usage: We must specify the root key with the @rootkey parameter and an individual key with the @key parameter. Please note that if the key doesn’t exist (without any warnnig) it would be created in the registry. The @value_name parameter designates the data item and the @type the type of the data item. Valid data item types include REG_SZ and REG_DWORD . The last parameter is the @value parameter, which assigns a value to the data item. Let us now see an example which would add a new key called " TestKey ", and a new data item under it called TestKeyValue :

Screen scraping using XmlHttp and Vbscript ...

I wrote a small program for screen scraping any sites using XmlHttp object and VBScript. I know I haven't done any rocket science :) still I thought of sharing the code with you all. XmlHttp -- E x tensible M arkup L anguage H ypertext T ransfer P rotocol An advantage is that - the XmlHttp object queries the server and retrieve the latest information without reloading the page. Source code: < html > < head > < script language ="vbscript"> Dim objXmlHttp Set objXmlHttp = CreateObject("Msxml2.XMLHttp") Function ScreenScrapping() URL == "UR site URL comes here" objXmlHttp.Open "POST", url, False objXmlHttp.onreadystatechange = getref("HandleStateChange") objXmlHttp.Send End Function Function HandleStateChange() If (ObjXmlHttp.readyState = 4) Then msgbox "Screenscrapping completed .." divShowContent.innerHtml = objXmlHttp.responseText End If End Function </ script > < head > < body > &l

Script table as - ALTER TO is greyed out - SQL SERVER

One of my office colleague recently asked me why we are not able to generate ALTER Table script from SSMS. If we right click on the table and choose "Script Table As"  ALTER To option would be disabled or Greyed out. Is it a bug? No it isn't a bug. ALTER To is there to be used for generating modified script of Stored Procedure, Functions, Views, Triggers etc., and NOT for Tables. For generating ALTER Table script there is an work around. Right click on the table, choose "Modify" and enter into the design mode. Make what ever changes you want to make and WITHOUT saving it right click anywhere on the top half of the window (above Column properties) and choose "Generate Change Script". Please be advised that SQL Server would drop actually create a new table with modifications, move the data from the old table into it and then drop the old table. Sounds simple but assume you have a very large table for which you want to do this! Then it woul