Incident log
When an error occurs in our process, it is a good idea to record. In a log why the error occurr and how it was resolv. Sometimes, errors occur not because our process is wrong but because there is an inconsistency in the data. For example, if the process searches for the ID of a record with a date, but there are two records with the same date, SQL will not know which one to take and the process will fail. So the corresponding corrective action is taken and record in the log for possible future exceptions.
Separation into functions
>>>>lass=”yoast-text-mark” />>When we handle large amounts of information, it is normal for cameroon phone number library the processes we develop to have a large number of instructions, resulting in very long code. The use of functions in SQL allows us to simplify the code in certain sections where we ne to obtain a value. We can call the functions over and over again from our procures.
Cursor management Some people
</p>
argue that it is not good to use cursors because they are supposly “slow”, but I think that there are times when it is unavoidable, and even very useful, since the use of cursors will allow us to linkin will allow you to better manage your accounts with the new business manager platform advance record by record and specify one or more instructions in each t
urn. When choosing to use cursors, we must be careful to close them correctly, mainly when using nest cursors (cursor inside another cursor). Another thing to take into taiwan lead account is that if an error occurs within the cursor, let’s say in an INSERT, when we handle the exception, we must also close the cursor(s) involv. On the other hand, to advance record by record, not only the cursor option is available but also the WHILE instruction, but it would be a matter of checking which of these options best suits our nes.