I have run Suse v6.4 and v7.3 successfully. Recently purchased v8.0 professional. Too replace win2k. I configured my network card with yast2 very simple ip address, subnet mask,DNS, Gateway, done. Trouble is it doesn't work. I do not have access to the rest of my network. Also no internet. I cannot ping any other box. I can successfully ping the linux box nic using its' ip address and loopback also works. I reinstalled win2k and I have access to everything on my network and the internet. I reinstalled Linux with the default setting, sans office and firewall, same problem. I also get a message in the console log that module c cannot be found. I get this error with three different installations. I haven't a clue what module c is and can find no referenjce to it any where. If anyone has a clue as to what is wrong please help. My config information is: Ifconfig eth0 Link encap:Ethernet HWaddr 00:A0:C9:ED:56:29 inet addr:192.168.0.9 Bcast:192.168.0.255 Mask:255.255.255.0 inet6 addr: fe80::2a0:c9ff:feed:5629/10 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:1 dropped:0 overruns:0 carrier:1 collisions:0 txqueuelen:100 RX bytes:0 (0 Kb) TX bytes:1764 (1.7 Kb) Interrupt:5 Base address:0x1060 Memory:fa126000-fa126038 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:34 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2308 (2.2 Kb) TX bytes:2308 (2.2 Kb) Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 netstat -tn Proto Recv-Q Send-Q Local Address Foriegn Address State
Hello SuSE folkz, 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? Thanks in advance for any responses. Alex
On Friday 14 June 2002 05:30 pm, Alex Daniloff wrote:
Hello SuSE folkz,
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? Thanks in advance for any responses.
Alex
Certainly tables that have many entries can take longer to find data in (table scans), but this is resolved by indexing the table. Indexes are usually created on primary keys, and you can add indexes on columns that you think you will be using frequently as search criteria. That will significantly improve SELECT statement performance. If you break up your tables due to length, what criteria will you use? Your application will have to know this criteria. What happens as new data is added and the tables grow? Will you create new tables automatically? It is better to design the application with a uniform data model than to break up the data model. Let the database handle that. If you are talking about extremely large data sets, that might be different. I have gotten good results from MySQL with tables that have over 1 million rows in my tests. hth, -ronc -- 7:13am up 10 days, 22:16, 1 user, load average: 0.08, 0.06, 0.01
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 ] [--------------------------------------------------------------------]
participants (4)
-
Alex Daniloff
-
Andrés A. Nogueiras Meléndez
-
hlb@byrdgrafxtech.com
-
Ron Cordell