S
slacroixak
Guest
Guys,I said at the very beginning I was not interested in AI. I can give a few reasons now: I know AI. It's NOT simple for everyone, more for DBA guys than for regular developers. At first, you need to enable AI for the wanted database, and administrate it when you switch AI files. The life cycle of AI files is tight to the database, I mean you cannot just loose AI files and make them again, as opposed as the single-incremental file I am talking about. A simple backup policy requires no enabling. A single script can do the job I mentioned. I can ask any developer to do probkup and prorest with a large full file and a small single-incremental file as I said. For my cases, AI has great chances to end up with larger files since all the transactions we do are updating or recreating the same records in a rather limited set of DB blocks. (it's a dev database) On one hand, an incremental backup is very quick (7 to 10 seconds), that's a very limited in time disk activity. On the other hand, AI lead to constant AI disk activity each time transactions occur, affecting the performance we are used to. (Normally, you handle AI on a separate Disk for performance sake etc...) At last, there could also be a few interesting licensing aspects, but it's not top of my head now
Continue reading...
Continue reading...