SQL Server cursors are immaculate when we need to work one record at any given moment, as OPPOSED to taking every one of the information from a table as a solitary bulk. Be that as it may, they ought to be utilized with consideration as they can influence execution, particularly when the volume of information increments. From an amateur's perspective, I truly do feel that cursors ought to be maintained a strategic distance from each time in such a case that they are badly composed, or manage an excess of data, they truly will affect system PERFORMANCE. There will be times when it is absurd to expect to evade cursors, and I doubt if numerous system exists WITHOUT them. In the event that you do discover you have to utilize them, attempt to lessen the number of records to process by utilizing a temp table first, and afterward assembling the cursor from this. The lower the number of records to process, the quicker the cursor will wrap up.  Please find below syntax for CURSORS widely used :

The process FLOW of CURSOR look LIKE below diagram: