30 Sep
2008
30 Sep
'08
11:52 a.m.
Hello,
I am trying to get out you knowledge as DBA ... in some discussions in
the past was brought out that in some cases doing a delete on primary
key followed by a pure insert might be faster than one update. It might
be dependent of DB server type and perhaps the question would have
better answer in appropriate db-specific mailing lists, but I want to
see if some of you has more experience/insights about this and is
willing to share or got into same dilemma.
Thanks,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
6 Oct
6 Oct
5:20 a.m.
Hello Daniel,
I can answer about Sybase: update is delete/insert, and optimizer will do it
more effectively the executing 2 different transaction.
Toly
miconda wrote:
Hello,
I am trying to get out you knowledge as DBA ... in some discussions in
the past was brought out that in some cases doing a delete on primary
key followed by a pure insert might be faster than one update. It might
be dependent of DB server type and perhaps the question would have
better answer in appropriate db-specific mailing lists, but I want to
see if some of you has more experience/insights about this and is
willing to share or got into same dilemma.
Thanks,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
_______________________________________________
Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
--
View this message in context:
http://www.nabble.com/-offtopic--update-vs-delete-insert-tp19739140p1983146…
Sent from the OpenSER Users Mailing List mailing list archive at Nabble.com.
11:12 a.m.
On Monday 06 October 2008, toly wrote:
I can answer about Sybase: update is delete/insert,
and optimizer will do
it more effectively the executing 2 different transaction.
Hi Daniel,
i think that doing a update is faster then doing two queries. The core need to
construct another SQL string, the DB need to be parse this and so on.. It
probably depend on the DB type, and exact configuration, but i doubt the
difference will be that relevant. Doing a delete and insert in two steps is
also different from the update that you have one small interval of
inconsisteny where the old record has been deleted, and the new one not yet
created (if you don't use transactions).
Aparently also for postgres an UPDATE is also the same as and DELETE/INSERT.
[1], which means its faster here too.
Cheers,
Henning
[1] http://archives.postgresql.org/pgsql-performance/2005-12/msg00589.php
5:01 p.m.
Hello,
On 10/06/08 12:12, Henning Westerholt wrote:
On Monday 06 October 2008, toly wrote:
ok. I was looking to use prepare statements or a stored procedure.
However, seems some db servers are doing it in this way, so probably
there are internal optimizations.
Thanks,
Daniel
I can answer about Sybase: update is
delete/insert, and optimizer will do
it more effectively the executing 2 different transaction.
Hi Daniel,
i think that doing a update is faster then doing two queries. The core need to
construct another SQL string, the DB need to be parse this and so on.. It
probably depend on the DB type, and exact configuration, but i doubt the
difference will be that relevant. Doing a delete and insert in two steps is
also different from the update that you have one small interval of
inconsisteny where the old record has been deleted, and the new one not yet
created (if you don't use transactions).
Aparently also for postgres an UPDATE is also the same as and DELETE/INSERT.
[1], which means its faster here too.
Cheers,
Henning
[1] http://archives.postgresql.org/pgsql-performance/2005-12/msg00589.php
_______________________________________________
Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
--
Daniel-Constantin Mierla
http://www.asipto.com
4:59 p.m.
Hello,
On 10/06/08 06:20, toly wrote:
Hello Daniel,
I can answer about Sybase: update is delete/insert, and optimizer will do it
more effectively the executing 2 different transaction.
good to know that some db systems are doing this way. Thanks!
Daniel
Toly
miconda wrote:
--
Daniel-Constantin Mierla
http://www.asipto.com
Hello,
I am trying to get out you knowledge as DBA ... in some discussions in
the past was brought out that in some cases doing a delete on primary
key followed by a pure insert might be faster than one update. It might
be dependent of DB server type and perhaps the question would have
better answer in appropriate db-specific mailing lists, but I want to
see if some of you has more experience/insights about this and is
willing to share or got into same dilemma.
Thanks,
Daniel
--
Daniel-Constantin Mierla
http://www.asipto.com
_______________________________________________
Users mailing list
Users(a)lists.kamailio.org
http://lists.kamailio.org/cgi-bin/mailman/listinfo/users
5683
days inactive
5689
days old
4 comments
3 participants
participants (3)
-
Daniel-Constantin Mierla -
Henning Westerholt -
toly