|
13 >> To retrieve space from a tablespace, just drop the
datafile, and delete the file from disk. Someone from
security will retrieve the personals from your cubicle, and drop
them in the mail after YOU'VE been deleted from the payroll.
14 >> You only need one user account in the database for
everyone to use. Sharing isn't always caring.
15 >> Go ahead -- apply every critical fix without testing
them first. It's probably MORE critical to make sure the fix
doesn't fix you first.
16 >> Don't keep a source code repository. The source is
current. "Current" can get cold in a hurry.
17 >> Give developers unrestricted access to the
production database. How about just popping open a can of
worms instead? If you let all the programmers design all the
tables because "they surely know what the applications need,"
then you're asking for chaos. And if you let programmers code
business rules and referential integrity into the app code
rather than into the triggers and/or constraints on tables, you
could be in for some trouble. Allowing developers to directly
modify production data is another place you don't want to go.
Unless you want to go hungry!
18 >> Surely every environment, database, or application
has the same set of code. It's better to assume they don't.
Better and safer.
19 >> Don't script anything, and don't save or document
what you've done -- you'll never need that stuff again anyway.Famous
last words that could turn into your infamous last day.
20 >> When new releases come out, upgrade ASAP and use all
the new features in each release. Just because Oracle
releases it, doesn't necessarily mean you need it. If you are
going to upgrade, don't do them in place just in case there are
problems or undocumented features. And read those release notes
on installing.
<< Previous
10 Mistakes
Back
Next
|
Home