Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualSky Warden

Posted 25 May 2013 - 04:15 AM

I'm not an expert in database management, but to me that number is too high for a database column or tables.

 

Have you ever heard about Dabatase Normalization? Simply, it's a concept of separating columns into tables and make relations to it. It's useful to avoid redundancy and dependency. It also will free your databases from some anomalies (deletion, update and insertion anomalies).

 

A character having a table just for its items is completely unnecessary. What if there's a new character? Making the same table (with only different names) over and over again is obviously redundant.

 

I'm wondering how could your database have that many tables and column. Can you please export your database and upload it here? That way I can analyze it and, if possible, make it more simple and effective. Trying to tweak something I can't see is hard. laugh.png

 

The row number is fine if the game is really big, but not for column and tables.


#2Sky Warden

Posted 25 May 2013 - 02:17 AM

I'm not an expert in database management, but to me that number is too high for a database column or tables.

 

Have you ever heard about Dabatase Normalization? Simply, it's a concept of separating columns into tables and make relations to it. It's useful to avoid redundancy and dependency. It also will free your databases from some anomalies (deletion, update and insertion anomalies).

 

A character having a table just for its items is completely unnecessary. What if there's a new character? Making the same table (with only different names) over and over again is obviously redundant.

 

I'm wondering how could your database have that many tables and column. Can you please export your database and upload it here? That way I can analyze it and, if possible, make it more simple and effective. Trying to explain something I can't see is hard. laugh.png

 

The row number is fine if the game is really big, but not for column and tables.


#1Sky Warden

Posted 25 May 2013 - 02:16 AM

I'm not an expert in database management, but to me that number is too high for a database column or tables.

 

Have you ever heard about Dabatase Normalization? Simply, it's a concept of separating columns into tables and make relations to it. It's useful to avoid redundancy and dependency. It also will free your databases from some anomalies (deletion, update and insertion anomalies).

 

A character having a table just for its items is completely unnecessary. What if there's a new character? Making the same table (with only different names) over and over again is obviously redundant.

 

I'm wondering how could your database have that many tables and column. Can you please export your database and upload it here? That way I can analyze it and, if possible, make it more simple and effective. Trying to explain something I can't see it's hard. :lol:

 

The row number is fine if the game is really big, but not for column and tables.


PARTNERS