3 ms·
Sorry friend, but this is a bit out of touch. Maybe that was the original design intent of SQL, but understanding the application's data model is beyond a lot o
by jeremyjh 4y ago
Sorry friend, but this is a bit out of touch. Maybe that was the original design intent of SQL, but understanding the application's data model is beyond a lot of sql analysts, much less their business partners.
- tremon 4y agoBut you don't want to do reporting on an application's data model, that doesn't scale: as soon as you have a medium-sized business, the data will not be confined to a single application (unless that application is named SAP). Understanding the business data model is a requirement for SQL analysts anyway, and once you have the application data transformed to the business model, the business users will have no trouble understanding it.
- jtdev 4y ago[dead]
- rezonant 4y agoHey, no one said it was easy. > but understanding the application's data model is beyond a lot of sql analysts You need a better data model or better data analysts (probably the latter). Putting analysts aside, I do agree though that the data model can be too complex for non-technical stakeholders, but in the vast majority of cases, the data model is simple and stakeholders are looking for basic statistical analysis and trendfinding. Also, if a moderately skilled human SQL analyst doesn't understand a data model, well GPT has no chance.