Re: Long-running queries

Ken Block writes: >In article <3uk28e$ccg@lennon.cc.gatech.edu>, gukal@cc.gatech.edu says... >Most solutions to the problem are to use multiple databases: one for >OLTP, and the second for DSS. In our database (a small one, about 400MByte) long queries slow down performance of that particular server process. The database itself isn't affected as sessions connecting to other server processes aren't slowing down. Something we are considering is to still maintain a single database but use two classes of DBMS servers - one for long queries and/or reports and the other for everyone else (actually we would have multiple sets of servers in each class). This is discussed in Ingres Tech Note US-35566. We haven't implimented this yet (still hashing out the details with developers) so I can't say how well this will work but I suspect it will work. Note that having two server processes running (one for long queries) should even benefit single processor machines. Steve.Croft@water.ca.gov DBMS Admin P.S. The normal attitude of the number of servers to start is along the lines of n-1 (where n is the number of processors > 1). Don't use this as a hard and fast rule as I can think of many situations (inlcuding the one described above) where you can overlook this rule.