Re: Oracle vs. MS SQL Server

From: DA Morgan <damorgan_at_exesolutions.com>
Date: Thu, 06 Mar 2003 17:41:11 -0800
Message-ID: <3E67F8B7.26EF18FF@exesolutions.com>

Joel Garry wrote:

> DA Morgan <damorgan_at_exesolutions.com> wrote in message news:<3E677A86.70CC2F9D_at_exesolutions.com>...
> > Joel Garry wrote:
> >
> > > "Richard" <qaz1521_at_hotmail.com> wrote in message news:<b42sl1$aba$1$8302bc10_at_news.demon.co.uk>...
> > > > There is a comparison report from PC Magazine at
> > > > http://www.pcmag.com/article2/0,4149,4154,00.asp
> > >
> > > Fairly interesting comparison, although my anti-PC bias can't help but
> > > discount it. And "Two general tools, SQL*Plus and SQL*Plus Worksheet
> > > (its Java-based equivalent) let you run SQL queries against databases.
> > > You still can't stop a long-running query..." makes me wonder if they
> > > know about interrupt keys or those little x's in the upper right hand
> > > corner... and they didn't seem to know about batch loading, or top
> > > sessions explain plan.
> > >
> > > <snipped>
> >
> > Makes me wonder whether you realize that closing a client session has zero affect on anything running
> > on a server: It doesn't. You can't kill a running statement or procedure by closing the client.

>

> I forgot all about that. I'm so used to just being in a command line
> on the server... [sigh].

>

> Of course, can't you x it and then go kill the session?

>

> >
> > Daniel Morgan

>

> jg
> --
> @home.com is bogus.
> "Walkin' round in women's underwear." - Mark & Brian Christmas cd.

KILL SESSION works
On Windows ORAKILL works
On UNIX KILL -9 works

There is always a way.

Daniel Morgan Received on Thu Mar 06 2003 - 19:41:11 CST