Re: HELP! SE versus Online AND is ONLINE faster than SE?

> > b) Improve throughput > > It is this latter I wish to discuss. > I've asked a co-worker who was involved in our upgrade and the pre-upgrade benchmarking to join this discussion. I don't know if he will or not, so I'll pitch in. There is little point in comparing SE to Online in terms of performance IMHO. SE is a VW. Online is a bus. If you are going to store by yourself to get a bag of groceries, then you should drive the VW. If you are going to the school to take a class to the zoo, then you should drive the bus. The bus may actually be slower than the VW, but you only have to make one trip. This is a rather limited analogy. Online has some features that make it more efficient at certain tasks than SE. If your application performs these tasks then you will see an improvement by switching to Online. If not, then you may not. Is there anybody out there who is running a multi-GB database with 100+ users on SE? (there will be one or two) IMHO, if you want a database that is 100MB with 20 users then you should consider driving SE. If you want a database with 1GB+ and 100+ users then you should consider Online. Of course if you want to talk integrity, connectivity, OLTP - then the story changes. cheers j. _____________________________________________________________________________ Jack Parker - Hewlett Packard, BSMC Boise, Idaho, USA jparker@hpbs3645.boi.hp.com _____________________________________________________________________________ He who lives by the keyboard, dies by the keyboard. >thud< _____________________________________________________________________________ Any opinions expressed herein are my own and not those of my employers. _____________________________________________________________________________