CODEWITHSUNDEEP
azuredatabase-design
Ryan
Ryan

Reputation: 5546

Is this a correct choice for partition and row key in Azure table?

I have a table that stores the online status of a user.

columns(userid, IsOnline,date)

If the user is online, the Isonline bool flag is true, if it goes offline, the IsOnline bool is false. This way I can see between which and which time the user was online.

Would it be fine choosing partitionKey: userId, Rowkey: the date and time of the event

?

The user can not go on and off at the same time, so rowkey should be unique. I like about this that it keeps all data for a user on the same partition. Also does choosing the date as rowId make sorting more efficient?

Upvotes: 2

Views: 777

Answers (2)

Igorek
Igorek

Reputation: 15860

UserId is a good strategy for the PartitionKey

With respect to RowKey, I would suggest using "DateTime.MaxValue.Ticks - dateOfEvent.Ticks" formatted to max number of digits.

This will make your RowKey always be in the descending order and thus allow you to pick the latest status of the user without getting data from all of he partition

Upvotes: 7

Robert Greiner
Robert Greiner

Reputation: 29742

Sounds reasonable to me. This groups all of a given user's actions together in a single partition. Each action is then delineated by an individual row with the Timestamp for the key.

You might want to keep in mind that every row in Azure Table Storage has a Timestamp column that is populated automatically on create/update. You could consider using this column for your Timestamp but searching/sorting will be slow since it is part of the tertiary data set associated with a Table Storage row.

Upvotes: 0

Related Questions