What would likely be the complications when using the anchor modeling ?
It would be highly unlikely to assume that the anchor modeling is absolutely perfect.
And to make better informed decision, I think knowing the likely inconvenience that can be encountered, when using the anchor modeling would be highly useful. However I couldn't find any inconveniences posted anywhere. Could you please elaborate what could be the likely inconveniences that can be faced when using the anchor modeling?
Re: What would likely be the complications when using the anchor modeling ?
If it is important for you to keep the number of tables small in your database, 6nf and anchor modeling is probably not your best choice. Even though the views will make your 6nf model look like a 3nf database implementation (and the triggers make it behave like 3nf), there will be more tables in an 6nf database model compared to a 3nf database model.
If your domain is static and your sources are very stable (most likely not to change at all) it might be a bit overkill to use AM.
The AM modeling tool generates only SQL Server and Oracle (for some Oracle versions) code at the moment. If you want to use another dbms then you have to change the generated SQL code to fit that dbms.