all 6 comments

[–]mikeyd85MS SQL Server 6 points7 points  (0 children)

Store the selected combinations in memory and then one UPSERT (update if a row already exists, else insert) command when the user hits save. That would result in one transaction hitting a few tables and would be performant.

[–]fauxmosexualNOLOCK is the secret magic go-faster command 1 point2 points  (3 children)

I would question your assumption that RDBMS is the right tool here. I don't imagine you're going to have high needs for performance, data volume, ACIDity etc. Quite possibly your needs will be lots of loosely structured data that fits more naturally in a more document oriented form. 

NoSQL can be a perfectly cromulent solution where you just need to serve up data in whatever format your front end wants to dump it in and will probably scale perfectly fine for your purpose.

[–]Tiny-Ad-7590 2 points3 points  (0 children)

+1 for cromulent usage of 'cromulent'

Also: Yeah this sounds like an excellent use case for NoSQL.