What topic/subject/thing do you believe you are more knowledgeable of than any other forum member?

[Citizen of Legoland]

This is the whole problem your schematic IS a database designed system. You are entering scores which should be a table in a database and the calculations (especially the ranking) should be done DB side. Excel should only be your front end for viewing the data. Doing it all on the DB side means you are free to choose the front end as well; tableau, excel, c#, html, it really doesn't matter what front end you use.

The issue with holding calculations in the database is that it restricts the user to what is set up by the developer - this is old style. Modern data discovery solutions encourage the calculations to be done front end so as to enable them to be based on user selections. Take the ranking example, and you have pre-calculated the results in the back end. What if the user wants to see the ranking based on a subset of the data, that would probably change the ranks. Pre-calculations were needed traditionally to speed up response times but with the improvement in RAM and reduction in costs and better front end software (Tableau being one) it isn't needed any more.

And Excel is gash.

 

[acquiesce]

WW2 American naval battles in the Pacific theatre
Great Lakes shipwrecks
American craft beer

 

[blueian99]

Pensions, sadly.

 

[Balti]

clitoris massage

 

[TFC]

I'd be surprised if anyone else on here had extensive knowledge of the management of ultradwarf bermudagrass in the SE United States...but you never know ;)

 

[BerkshireBlue]

The issue with holding calculations in the database is that it restricts the user to what is set up by the developer - this is old style. Modern data discovery solutions encourage the calculations to be done front end so as to enable them to be based on user selections. Take the ranking example, and you have pre-calculated the results in the back end. What if the user wants to see the ranking based on a subset of the data, that would probably change the ranks. Pre-calculations were needed traditionally to speed up response times but with the improvement in RAM and reduction in costs and better front end software (Tableau being one) it isn't needed any more.

And Excel is gash.

If you read my previous posts you will realise we are on the same page as I've mentioned all of what you said before.

 

[Citizen of Legoland]

If you read my previous posts you will realise we are on the same page as I've mentioned all of what you said before.

You said that the aggregations should always be DB side, I disagreed.

 

[BerkshireBlue]

Nope. Previously I said use tableau/alteryx if you bothered reading you're just repeating exactly what I said.

 

[Citizen of Legoland]

Nope. Previously I said use tableau/alteryx if you bothered reading you're just repeating exactly what I said.

So you're saying the calculations should NOT always be done DB side, if so then we agree.

 

[BerkshireBlue]

So you're saying the calculations should NOT always be done DB side, if so then we agree.

Correct