I will be posting an updated version of the data mart design process using SQLite later this year. There are a lot of examples where the data mart design is useful for localized analysis/data science projects rather than enterprise scalable or service oriented deployment. Instead of using a Microsoft tool, I will be showing how all of the data engineering (ETL) is done using Python and SQLite. I'll see if I can include a part of the FACT table example where the ID is not available in a staging table.

This would be a useful feature. However, I'm not sure that it is available via the server-side. Most likely you would have to write JavaScript to accomplish this. Either way, it doesn't look like an easy process to do. Someone should contribute to the Dash project a module that makes this feature easy for developers.

The example simply shows how SQL was allowed with no defense built into the design. Discovering object names, such as tables or variables, is another topic.

Literally he showed in this video how he can accessed to the db if it's not secured! Watch it again! Quite clear explanation to be honest!

The example I recorded here just shows a complete disregard to security. The developer is allowing SQL to be injected within the C# code. A stored procedure would be a better practice. However, it is not excluded from attack if not properly developed.

Get a login stuff simple and let the user only adding any infos after authenticated and give to method an [ Authorize ] attribute or the page! Check Identity stuff and you don't need to worry about so much!