Re: Problem with the sysmaster database.

Jiten Thakkar said: > > Hi , > > Environment : > Hardware : Sun4u-Sparc/Ultra > O/S : Solaris 8 > Informix : 9.30.FC2 ( 64 bit) > > I have a database with 40,000 tables. The data warehouse application > creates > new tables to store the information for new products. "Interesting" design. > My problem is the query on SYSMASTER database is very slow. A simple > select > from syslocks ( select * from syslocks where tabname = <some_table> ) > takes > 5 minutes. I have run updates statistics on this table. My fact table has > 2 > million rows and the select for one of the rows comes back immediately. > Can > somebody suggest how to improve the performance of the SYSMASTER database > ? Not all the tables in sysmaster are physical tables, most of them are actually maps to shared memory structures. It's pretty much impossible to performance tune it. -- Bye now, Obnoxio "C'est pas parce qu'on n'a rien ` dire qu'il faut fermer sa gueule" - Coluche did i mention i like nulls? heck, i even go so far as to say that all columns in a table except the primary key could/should be nullable. this has certain advantages, for example, if you need to insert a child record and you don't have a parent row for it, just do an insert into the parent table with the primary key value (everything else null), and voila, relational integrity is preserved. but this is, admittedly, a bit controversial among modellers. --r937, dbforums.com sending to informix-list