Since it's kind of slow here at tek-tips, let's have some fun
The best way to learn SQL server is to make a mistake on the production server
Here are 3 of mine
Script out a table to make a history table and forgetting to change the name in the drop statement.... ooops
Scripting out procedures and have drop dependent objects checked.... oops
Selecting an Update statement and hitting F5 and then realizing you didn't select the WHERE clause... oops
Needless to say once you do this on a production box and you have to go back as fast as possible you will never do these things again
Of course backup DB and restore in time to a minute before the mistake happens is a lifesaver
Now these are mine, not as bad as that DBA in Utah who truncated a table before checking that the new file was there and then they had to stop every single train in the state for 4 hours
Now these are mine, how about yours..don't be embarrassed , let's hear it
Denis The SQL Menace
SQL blog:
Personal Blog:
The best way to learn SQL server is to make a mistake on the production server
Here are 3 of mine
Script out a table to make a history table and forgetting to change the name in the drop statement.... ooops
Scripting out procedures and have drop dependent objects checked.... oops
Selecting an Update statement and hitting F5 and then realizing you didn't select the WHERE clause... oops
Needless to say once you do this on a production box and you have to go back as fast as possible you will never do these things again
Of course backup DB and restore in time to a minute before the mistake happens is a lifesaver
Now these are mine, not as bad as that DBA in Utah who truncated a table before checking that the new file was there and then they had to stop every single train in the state for 4 hours
Now these are mine, how about yours..don't be embarrassed , let's hear it
Denis The SQL Menace
SQL blog:
Personal Blog: