Check your manuals, environment variables, configuration files for both sorting and SQL parallelism. Separate the system catalogs from the various types of logs in different database partions. Separate very active tables from each other. A massive reorganization is a lot of work. Separate spaces and disk for the logs is probably the most payoff, followed by the most active tables.
Prevention is easier than fixing problems.
Help the developers to stop future problems. Get involved in design and code reviews. Show the developers how to analyze SQL for performance and avoid long transactions. The views and opinions expressed in this page are strictly those of the page author. The contents of this page have not been reviewed or approved by the University of Minnesota.