On Wed, 09 Nov 2011 04:00:12 -0000, "siddharthparashar"
<sparashar@...> wrote:

> Thanks guys for your prompt response.
>
> I doubled checked and these particular machines are not HP.
>
> Also it's a single HDD with no RAID and does not support either read or
> write caching. I mean this particular model does not support this.

Every HDD has some amount of read and write caching.

> Another observation that we made is with transactions. Tae following
> example -
>
> 1> insert hundred records in a table
> 2> after each record is inserted, commit the transaction.
>
> Now these steps give different output on different machines. On Windows

7

> and XP they give results in 1.5 seconds.
>
> But on Windows 2008 R2 this takes 22 seconds. Now when we changed the
> application to commit at the end or hundred inserts then output was

almost

> same on both the machines.

You might want to check if the Windows Server 2008 R2 is installed as an
Active Directory server (or uses the configuration profile for an Active
Directory server). Active Directory servers are notorious for their bad
performance for other services as Windows will disable almost all caching
to make sure all change to the AD are immediately committed to disk.

I am not 100% sure which options you would need to change, but with a bit
of googling you should be able to find info on this.

Mark