J
James Palmer
Guest
Unfortunately, whilst this is a good idea in theory, Tkerk, in practise it may not be so easy with legacy applications. In our case, we have 5 databases for legacy reasons, of which only really one is written to in practise. It would make sense to get rid of the others as you say, but the codebase is littered with DBNAME.TABLE.FIELD phrases, each of which would need visiting in order to fix them. It's a massive overhead that businesses don't want to swallow, even if you explain the risks to them.
Continue reading...
Continue reading...