We optimized our reporting and slowed down our data input!

  • We have a SQL Server 2K5 DB Application (with Merge Replication Involved) and we were having performance issues with Reporting (they took too long to generate). We introduced Maintained Views to reduce our reporting times and discovered that most of our data input functions through our front end GUI have ground to a halt. Our front end is Delphi 7 using ADO components to access the DB.

    How can we increase the speed of our reports without compromising speed of data input?

  • A lot of it will depend on your data structure (tables), indexes, etc.

    Another important question is whether the reports need to be real-time, or if they can be cached in a warehouse.

    - Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
    Property of The Thread

    "Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon

  • Do you mean indexed views?

    More details would help. It would be good to know as well what the input rate is, perhaps using a trace to determine where things are slowing down.

  • And (broken record time) the execution plans for the queries that are causing you the most pain.

    "The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
    - Theodore Roosevelt

    Author of:
    SQL Server Execution Plans
    SQL Server Query Performance Tuning

  • Thank you very much for your input. We are going to investigate a few of the things that were mentioned and we'll post back with some results or possibly a few more questions.

    Thanks again.

Viewing 5 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply