Dynamic SQL is a bit slower, but not horribly so. I’ve actually dug into the ORAthis, ORAthat which Oracle uses for its internal interface, and it ends up boiling down to something that has to be parsed at run time anyhow.
I know less about Javascript — that system apparently doesn’t understand when you’re asking to load the same code more than once, and optimize it for you?
Dude, we need to talk. It's awful.
Dynamic SQL is unacceptable on speed issues (no compiling) and on Best Practices issues (no Reflection, no ability to use Perf Monitor or Execution Planner, just to name two optimizer technologies.) I suspect you are not in Big Data at all. DON'T ALLOW DYNAMIC SQL.
I’ve actually dug into the ORAthis, ORAthat which Oracle uses for its internal interface, and it ends up boiling down to something that has to be parsed at run time anyhow.
I'm more talking SQL, I don't have Oracle. Oracle might differ. But I know my SQL.
I know less about Javascript — that system apparently doesn’t understand when you’re asking to load the same code more than once, and optimize it for you?
Not in ASP.NET 3.5 codebase. They might have cleaned it up in 4.0 or 4.5, but I stick with MVC now, and get my Ajax using RAZOR.
PeopleSoft, the #2 or #3 largest ERP install base in the world uses 100% dynamic SQL.
But is is repeatedly CALLED, not REPEATED.
Note: the schema for a typical PS database runs into the 10s of thousands of tables/views. And no DB-level Referential Integrity (which makes sense for their architecture).