Like the list of country-codes, with their names?
Michael Sterling wrote:
1. Large tables (whereas Large is not not an absolute value , but rather larger in comparison to other tables)
Like the list of country-codes?
Michael Sterling wrote:2. Tables with many linked tables attached (for example orderHeaders orderDetails etc.)
Tables with lots of null values are badly designed.
Michael Sterling wrote:3. Fields with large variance (fields that all values within are null or 0 NOT important)
Do you keep such information?
Michael Sterling wrote:4. Frequently changed fields ( If users updated table records yesterday and a day before it is important)
I would love that; often you see a dot (.) for a required field in the db.
Michael Sterling wrote:5. Fields with Meaningful text inside
Then they should not be on the list. If I order a car, I quote what I need, without adding the text that there is more coming that I don't know yet. Focus on what you do know, and you can extend it later.
Michael Sterling wrote:6. more properties I'm not thinking about right now....
I'd not use an AI, just to be able to say there is AI in there. Start with finding a way to get the amount of daily traffic from a record, and work from there
Michael Sterling wrote:How would you approach and design this kind of algorithm ? since it involves data modeling , analytics and AI all together...
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
"If you just follow the bacon Eddy, wherever it leads you, then you won't have to think about politics." -- Some Bell.