[Guest4390857394857]

....

[Vince]

1) I don't believe there's a particular limit. Just what your (physical) server can handle. Let's take these forums for example. Each page request takes approximately 12 queries. There are 900 users online. You do the math.
2) The hard upper limit is 1000 columns (InnoDB). However, I wouldn't use more than 30-ish for one table. Don't make too many columns. Make more tables and more rows instead. Then use joins to assemble the data you want from the different tables.

See my tutorials on database normalization here and here. The second one may be a bit easier to follow because it has images.

[Guest4390857394857]

....

[Vince]

Quote:

Originally Posted by ShivRp BTW what if i have more than 30 columns in the sql server? What would happen wrong?

Nothing. It's just bad practice and usually an indication that your database isn't properly normalized and that you aren't using MySQL correctly. Once particular data duplicates across multiple tables then that data should be linked from a separate table. Say, if you identify a player's properties by name. If the player changes his name you'd need to update it in their account, in the houses table, in the business table, and wherever else it might be used.

[Guest4390857394857]

....