Pure performance after restoring to different server

Hi All,
When I restore our production database that run very well to the
different server the performance becomes very pure. I am using DOTNET
front end app to access the database.
Can anybody tell me how do I go about this problem.
Is there some kind of checklist that I can go through or is there some
options that I didn't set when I did restore operation (like my be
statistics,etc).
I've checked the indexes and they all seem to be in place.
The server itself hardware-wise is identical to the production one.
Any help is greatly appreciated.The first step is to run Profiler and get the duration of your queries on
the old server vs. the new server. This will tell you if it's the database
server that's taking the extra time or if it's network latency, poor
connection, or some other problem.
"UnkleVo" <isharko@.att.net> wrote in message
news:a3538463.0403240818.1a23655e@.posting.google.com...
> Hi All,
> When I restore our production database that run very well to the
> different server the performance becomes very pure. I am using DOTNET
> front end app to access the database.
> Can anybody tell me how do I go about this problem.
> Is there some kind of checklist that I can go through or is there some
> options that I didn't set when I did restore operation (like my be
> statistics,etc).
> I've checked the indexes and they all seem to be in place.
> The server itself hardware-wise is identical to the production one.
> Any help is greatly appreciated.