We use seagate to generate reports for our users. It is performing really badly and we think It might be to do with seagate using tempdb and creating exclusive locks and making everything run slowly. I am new to all this so that might not have made much sense. If anyone can shed anylight on the subject that would be amazing!!

Thanks Meg

-- Anonymous, March 01, 2002

Answers

Meg,

My suggestion is to first find out if it is the SQL statement or Seagate Crystal Reports engine.

Take a SQL query you know is slow/CPU intensive thru Seagate Crystal Reports and execute it in SQL Server's Query Analyzer. If it is slow there, then use processes to optimize the query. Indexes and/or views in the database may help.

If the query executes fast in QA and is slow thru Seagate Crystal Reports, then you know to look at what the report engine is trying to do with your report.

Good Luck,

Eric

-- Anonymous, March 06, 2002