Abstract
It is very common to find database applications that use cursors to process one row at a time. Because data manipulation through a cursor in SQL Server incurs significant additional over-head, database applications should avoid using cursors. T-SQL and SQL Server are designed to work best with sets of data, not one row at a time. If a cursor must be used, then use a cursor with the least cost.
This is a preview of subscription content, log in via an institution.
Buying options
Tax calculation will be finalised at checkout
Purchases are for personal use only
Learn about institutional subscriptionsPreview
Unable to display preview. Download preview PDF.
Rights and permissions
Copyright information
© 2009 Grant Fritchey and Sajal Dam
About this chapter
Cite this chapter
(2009). Cursor Cost Analysis. In: SQL Server 2008 Query Performance Tuning Distilled. Apress. https://doi.org/10.1007/978-1-4302-1903-3_14
Download citation
DOI: https://doi.org/10.1007/978-1-4302-1903-3_14
Publisher Name: Apress
Print ISBN: 978-1-4302-1902-6
Online ISBN: 978-1-4302-1903-3
eBook Packages: Professional and Applied ComputingProfessional and Applied Computing (R0)Apress Access Books