From the office wiki...
-
A coworker's explanation of why we should all use transactions:
... what? I'll forgive anyone the use of imperfect english, but even so this fails to make any sense.* Although transactions are parts of the foundation of Transact SQL, for the purposes of human beings they are useless if need to be rolled back or restored. With a logical operation into a transaction we have simplicity in a process that otherwise will be hell to get right, w/out overrunning the whole database. We cannot backup the table constantly for all tables and make it work, but transactions do not involve tables but operations therefore tables do not have to be changed nor re-inaugurating the schema is necessary.
-
Run...
-
When nine-hundred years old you become, sound as good your English will not!
-
* Although transactions are parts of the foundation of Transact SQL, for the purposes of human beings they are useless if need to be rolled back or restored. With a logical operation into a transaction we have simplicity in a process that otherwise will be hell to get right, w/out overrunning the whole database. We cannot backup the table constantly for all tables and make it work, but transactions do not involve tables but operations therefore tables do not have to be changed nor re-inaugurating the schema is necessary.
This is the guy who took database snapshots each second and restore them when the user press Ctrl-Z we all have heard about.
-
Well, that's wikis for you.
The good thing about wikis is that any smart person can correct errors.
The bad thing about wikis is that any idiot can create errors.
The REALLY bad thing about wikis is that the idiots grossly outnumber the rest of us.
