Shawn <[EMAIL PROTECTED]> writes:
> The query just ran and here is the basic output:
> UPDATE 15445
> Time: 22121.141 ms
> and
> explain ANALYZE update shawns_data set alias = null;
> QUERY PLAN
>
>
Ok,
The query just ran and here is the basic output:
UPDATE 15445
Time: 22121.141 ms
and
explain ANALYZE update shawns_data set alias = null;
QUERY PLAN
--
On Aug 29, 2007, at 5:15 AM, Jens Reufsteck wrote:
I'm having a strange performance issue with two almost similar
queries, the
one running as expected, the other one taking far more time. The only
difference is that I have "uniid in (10)" in the normally running
query and
"uniid in (9,10)" in
Hi Tom,
Thanks for replying.
There are no FK's, indexes, or dependents on the alias field.
The system is in the middle of its weekly full activity log resync,
about 600 Million records. It will be done later this evening and I
will run the explain analyze thenand I will post the results. I w
Shawn <[EMAIL PROTECTED]> writes:
> update shawns_data set alias = null;
> Alias is a type varchar(8)
> The table has 26 fields per record and there are about 15,700
> records. The server hardware is a dual QUAD-CORE Intel 2 GHz XEON dell
> 2950 server with 4 drive SAS RAID-5 array, and 16G of R
Hello,
I have a recurring script that updates some tables from an MS_SQL
server. One of the operations sets a field in all records to null in
preparation of being updated with values from the other server. The
SQL statement is:
update shawns_data set alias = null;
Alias is a type varchar(8)
T
