Xref: alice comp.databases.oracle.server:73786 Path: alice!news-feed.fnsi.net!netnews.com!newspeer.monmouth.com!nf1.mgmt.sympatico.ca!news1.bellglobal.com!news21.bellglobal.com.POSTED!not-for-mail Sender: stark@HSE-Montreal-ppp19485.qc.sympatico.ca Newsgroups: comp.databases.oracle.server Subject: oracle tuning From: Greg Stark Organization: People's Front Against MWM Message-ID: <873dubv5sj.fsf@HSE-Montreal-ppp19485.qc.sympatico.ca> Lines: 15 User-Agent: Gnus/5.070095 (Pterodactyl Gnus v0.95) Emacs/20.3 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 12 Nov 1999 20:00:53 GMT X-Trace: news21.bellglobal.com 942436853 209.226.190.191 (Fri, 12 Nov 1999 15:00:53 EDT) NNTP-Posting-Date: Fri, 12 Nov 1999 15:00:53 EDT We have a largely OLTP database driving a web site where I imagine discrete transactions would be a really big win. However there are occasional queries that do full table scans to generate reports or queries. Will enabling discrete transactions cause those queries to break completely? (with "snapshot too old")? Or is there a strategy for dealing with this -- only using discrete transactions when no big queries are running, for example. And if I enable "discrete_transactions_enabled" is that all I need to do or do I have to change every sql call to make it a discrete transaction and fall back to normal transactions? -- greg