Without branding, Dynamic Data applications can be created in minutes. This is for your RAD web developer who doesn't care about the user interface layer. This will only work well for an intranet scenario. However, the MVC line focuses on very different scenarios.
Asp.net Dynamic Data Web Application combines multiple layers into one. I know that Object Relational Mapping (ORM) is supposedly the future, but when layers are not displayed, this can cause serious optimization problems and make testing almost impossible. This applies to both the ADO.NET Entity Framework (EF) model and the LINQ to SQL model. These are the only model cell providers available for a web application with Asp.net dynamic data objects. They do not work well, if at all with Microsoft Access.
However, when the time to create the right solution is short, Microsoft is inventive when it comes to dirty ways to write applications. A dynamic data website is one of those technologies that add to their nose. You may be ready to architect the Sql Server database approximately because you expect that you will have to make changes to it later. If you want to quickly find out about a website that you want to snatch later when you have more time. Astronomical web applications Asp.net for web applications for you? EF comes to foreign keys to certain relations.