[dba-SQLServer]Rolling back a transaction log?

Well it finally happened... We have a Complaint database that runs in
conjunction with a goldmine database.  The Goldmine database tracks outgoing
calls made by our company to customers in order to track sales leads and now
complaints.  Since 4/1/2002 we have not had a database error or hiccup until
now.  The company's official DBA, while working on a development database on
the production server (yes, that's right) inadvertently wiped out my
database instead of his test one this morning, The users of the Complaint db
suddenly began to complaining that there were no records, and upon checking
I found this to be the case.  I backup every night, and I have the log file
backup when it reaches 60%.  BUT.  I did not have *ANY* protection for the
moments before the wipe out.  Initially I panicked about not being able to
kick the users out quickly enough... I didn't bother to *remember* that I
had a Kill All Users In Db script.  So about 10 minutes later (after kicking
all the users out) I restored the database back to last log backup, but that
was not good as it had the transactions that wiped out the database.  SO I
had to restore to last nights copy officially killing all entries from 10am
and prior. :(

I've secured my script for killing Active Users in the DB.  And My boss
knows *who* wiped out the database, in fact I made sure he knew as soon as
it happened ... maybe that's not a good political move, but I'm in charge of
the db.  Now the question is... Since the log file is only 1meg long and on
average it doesn't backup the log for perhaps every 2 to 3 days... (I do
make a full backup every night).  I suppose I could manage the backups to
include incremental changes every hr, so that as little data is lost?  What
do you guys suggest?


-Francisco
http://rcm.netfirms.com