Skip to main content
Database Administrators

Return to Question

edited body; edited title
Source Link
marc_s
marc_s
  • 9k
  • 6
  • 45
  • 52

Seperate Separate table by often changed / not often changed data?

I have a application which querys different gameservers, and stores for example if the server is online, and how many players are connected. But of course there isis also data which is changed rarely. Currently

Currently I have all this in one table.

So my question is: Doesdoes it make a performance difference if iI split this table up, so that often changed data is in one table, and things like the description in another?   

(I have to add that I always only select the data I need, so not like Select *Select *). But when I select the data I often have to select the often changed data + the rarely changed data at once.

Seperate table by often changed / not often changed data?

I have a application which querys different gameservers, and stores for example if the server is online, and how many players are connected. But of course there is also data which is changed rarely. Currently I have all this in one table.

So my question is: Does it make a performance difference if i split this table up, so that often changed data is in one table, and things like the description in another?  (I have to add that I always only select the data I need, so not like Select *). But when I select the data I often have to select the often changed data + the rarely changed data at once.

Separate table by often changed / not often changed data?

I have a application which querys different gameservers, and stores for example if the server is online, and how many players are connected. But of course there is also data which is changed rarely.

Currently I have all this in one table.

So my question is: does it make a performance difference if I split this table up, so that often changed data is in one table, and things like the description in another? 

(I have to add that I always only select the data I need, so not like Select *). But when I select the data I often have to select the often changed data + the rarely changed data at once.

Source Link
Sapd
Sapd
  • 101

Seperate table by often changed / not often changed data?

I have a application which querys different gameservers, and stores for example if the server is online, and how many players are connected. But of course there is also data which is changed rarely. Currently I have all this in one table.

So my question is: Does it make a performance difference if i split this table up, so that often changed data is in one table, and things like the description in another? (I have to add that I always only select the data I need, so not like Select *). But when I select the data I often have to select the often changed data + the rarely changed data at once.