Multiple choice technology architecture

A batch program in SQL Server 6.5 takes 3 days to complete, even though management would like it to finish in 3 hours. What is a very likely cause of poor performance?

  1. Bad index management

  2. Network delay

  3. Use of SQL Server 6.5 instead of 7.0

  4. Limitations of Microsoft technology
Reveal answer Fill a bubble to check yourself
A Correct answer
Explanation

A 24x performance gap (3 days to 3 hours) strongly suggests missing or poorly designed indexes causing full table scans. Without proper indexes, SQL Server must read every row for each query, turning efficient lookups into massive sequential operations. Network delays or version differences wouldn't cause such extreme slowdowns.

Keep practicing — related questions