# SQL Server Question: How to go about using a collection of cards

So basically I'm new to SQL Servers and for that matter generally to Server Logic and Server behavior. (Used to only work on single player games) OK, so my questions is as followed. Lets take Hearthstone for example every user has a card collection. Now if using an SQL server, I can create tables for the users, I can also create tables for the cards, but how do I combine those? To be more specific my solution would have been to make a new table where the playerid and the cardid is stored with the value of how many of the certain card the player has.

However, my issue with this solution is that, if we assume we have 1000 players and we have like 500 cards then the table will be clustered with entries of same playerid's who have different cards.

Basically my question is: Is there a better solution for this and if not what is the capacity of SQL tables/Servers, like when can i expect a drop off during loading the collection of a player who has all 500 cards for example?

Since I'm new to SQL I might also be having a wrong idea on how to solve this issue, so if there is another solution or I'm missing something I would appreciate if someone pointed me in the right direction.

Your hunch is reasonable: you'd create a third table, a CardOwnership table or some such, that has (at least) columns for player ID and card ID. You'd probably use a clustered index on the player ID for this table.