Hi, Alex
Could somebody experienced in SQL DB answer this question.
Assume that all tables in DB have the same number of columns e.g.10. What is better for DB performance to have few of bigger/longer tables or lot of smaller/shorter tables?
I think that this is not a trivial question. The first approach to build a DB is "a lot of thinking" on how information should be in the tables. Then make a second approach building a small-data almost-real-structure of the DB and play queries (data in and out) as in the real application. This last step refines the structure of the DB tables. And finally go and play. If you find that the structure was not good, don't worry, you can easily recreate a DB, because there are plenty of commands to perform queries joining data from two tables and putting in a third one. If you can take a look at the book 'MySQL' from Paul DuBois, edited by News Riders. The first four chapters are the 'Tao Te Kin' of DB using. (What I mean is that they're clarifiying and educative rather than howto-tive) By the way, thanks for your help setting the two Xservers. I've finally found were SuSE starts the ".X.err". It's a predefined command insisde /etc/bash.bashrc. -- [--------------------------------------------------------------------] [ Prof. Andres Augusto Nogueiras Melendez ] [ Departamento de Tecnologia Electronica - Universidad de Vigo ] [ Campus Lagoas Marcosende, 9 http://www.dte.uvigo.es ] [ 36280 - Vigo, Pontevedra mailto:andres.nogueiras@dte.uvigo.es ] [ Spain tel: +34 986 812 091 fax: +34 986 469 547 ] [--------------------------------------------------------------------]