It wasn't literal tape, was backed up to another hard drive array as a full region dump. The DBA called them "tapes"IIRC.
It wasn't literal tape, was backed up to another hard drive array as a full region dump. The DBA called them "tapes"IIRC.
Flashback doesn't work with schema changes. If their reset query is like some I have used.. i.e. drop all tables and recreate, flashback data is totally gone. Real backups are much more dependable.
And yes I did drop a column on a 10 million row table in production, and was sad I couldn't flash it back. Took 8 hours to get the row back via tape and hand-edit the few changes since the backup from server logs. Sad day.
Okay TRWTF is there is some confusion in this thread about 32 vs 64 bit.
A 32 bit OS can address more than 4GB of ram. It is very common for Windows Server 2003 (32 bit) to run with 8 or 16 GB of ram (just a 2 or 3 GB per process limit).
However, windows XP (with very similar base OS to server 2003) is limited to 4 GB of ram. This was done on purpose by microsoft, becuase they wanted to encourage people with lots of ram to move to a 64 bit os.