Last month I was contacted by a company, they were complaining that since they have migrated from SQL Server 2000 to 2005 the performance of their web application is not only decreasing but sometimes the SQL Server stop responding and the only workaround the DBA was finding is the restart of services - sounds too painful.

I started Analyzing the machine configuration to see whether the machine is as per the requirements, the machine was 8 processor with 8 GB of RAM - more then enough. The Page File size and the Database Size were also as per the recommendation, then what's the problem?

I took more time to figure out by having few more questions.

Q-Were SQL Server 2000 and IIS running on the same machine?
A- Yes.

Q- After migration, doesn IIS running on the same machine?
A- No.

One of the obvious reason was the database design itself, but i was not touching the area because it might become an offense to the database design team.

Q- How the Database was migrated?
A- Using the Database Migration Assistant.

Another obvious reason, the migration tool can only migrate from 2000 to 2005 and can't change any logic - as the name complies.