Skip to main content
  • 591 Accesses

Abstract

The most dreaded call a DBA can get is this: “Everything in the application is slow! FIX IT!” In many cases, the database is one of the culprits of the poor performance of the legacy code. When you are approached to deal with some of these issues, what do you do? After painful code has been identified, you can perform triage for some immediate relief. Once that is accomplished, document the code thoroughly to identify any anti-patterns. This will help you as you rewrite the code using more performant techniques.

This is a preview of subscription content, log in via an institution to check access.

Access this chapter

Chapter
USD 29.95
Price excludes VAT (USA)
  • Available as PDF
  • Read on any device
  • Instant download
  • Own it forever
eBook
USD 39.99
Price excludes VAT (USA)
  • Available as EPUB and PDF
  • Read on any device
  • Instant download
  • Own it forever
Softcover Book
USD 54.99
Price excludes VAT (USA)
  • Compact, lightweight edition
  • Dispatched in 3 to 5 business days
  • Free shipping worldwide - see info

Tax calculation will be finalised at checkout

Purchases are for personal use only

Institutional subscriptions

Author information

Authors and Affiliations

Authors

Rights and permissions

Reprints and permissions

Copyright information

© 2020 Lisa Bohm

About this chapter

Check for updates. Verify currency and authenticity via CrossMark

Cite this chapter

Bohm, L. (2020). T-SQL Triage. In: Refactoring Legacy T-SQL for Improved Performance. Apress, Berkeley, CA. https://doi.org/10.1007/978-1-4842-5581-0_1

Download citation

Publish with us

Policies and ethics