Oh even better.... have you started to see the dribble that flows out of this movie and into your conference calls and meetings? http://www.imdb.com/title/tt1210166/ exhibits A-J http://www.hark.com/collections/zwvfsfqtbr-moneyball
good god all the names are taken
Posts
-
The Most Hated Buzzword - 2011 -
Gaming in 2012...I was on the Old Repubplic :zzz: :| - pretty much a fail, played for 3 months and was bored outta my mind Still playing a 2011 games RIFT/starcraft2... annoying :mad: but fun And impatiently waiting for the secret world :omg: . http://www.thesecretworld.com/ already picked up the lifetime sub. If you like pvp.. check it out... looks very epic. http://tsw.guildlaunch.com
-
ISP hackedone can only hope this is the mistake of the internal communications team and not the Infrastructure Team writing this. My guess is the marketing group heard a acronym and confused the DB codepage with the encryption type... marketing people eyes tend to glaze over when technical jargon is slung around. Thats why we keep the pretty people away from the smart people. :)
-
Some DBA jokesAwesome, hadnt heard any of these! If i wasnt so happy on irish coffee I would take defense! here are some more oracle based ones. http://www.orafaq.com/wiki/Fun\_stuff DB2 doesn't make funnies!
-
The best DBA of all timeHes not a DBA then, or he is a dba in training... its a common mistake, and usually and honest one... however... he could be right if there are less than 5 columns and the RDBMS does not allow clustering of columns in the indexes... overall though you are correct, this is usually a terrible idea. The maintenance on this would be bad even for a small table and wasting CPU cycles (I know most everyone does not code for CPU inefficiency in distributed systems, unless the cycles are above NN% or NNN% for Mutliproc)... Not to mention that an insert update or delete would be very much drawn out longer than it needed to be. A rule of thumb for MOST major RDBMS (DB2, Oracle, MSSQL, Mysql) no greater than 5 indexes per table. IF you stick to this and follow your rules for using multicolumn indexes, High Cardinalyty and some very basic rules for SQL writing (group instead of sortby, Predicate order, etc...) you can very efficiently make your code SING!
-
How far do you go with your backupsAt work, We have 2 SANS and use TSM... SANS are in 2 geodiff areas (3 miles apart), I backup incrementally 4 times a day. Sometimes more for giant DB's. My Workstation gets a backup weekly. At home, i have 3 jump drives that i rotate between the home office and the work office, and then i also have 2ea 500 GB external HDD's. I lose a PC about every 6 months, then i have to fix it.... so i am quite used to implementing HADR at home, Bare Metal Restores FTW!