Not sure if this is right place to ask this but...

We have just upgraded an SQL Server from SQL 2000 to SQL 2005 and are experiencing problems with some Crystal Reports.

When on SQL 2000 certain reports, although large, would take about 10 seconds to run. Since upgrading to 2005 these reports are taking 2 - 3 mins. When the SP executed by the CR is obtained from profiler and run in Management Studio, the information is returned in less than 5 seconds.

When viewed in profiler, the number of Reads (when run from CR) are 10 million plus. This has only happened since changing to 2005, and we have same indexes etc as when in 2000. We have added nolocks to SP's but this makes no difference.

Has anyone else experienced this or is there something we could try to solve this problem?

Thanks
Steve