Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

Execute immediate performance varies between clients

2 posts in Appeon (partner product) Last posting was on 2010-04-20 01:15:48.0Z
Michael K Posted on 2010-04-15 07:17:21.0Z
Reply-To: "Michael K" <michael.kench@stiearc.com.au>
From: "Michael K" <michael.kench@stiearc.com.au>
Newsgroups: sybase.public.appeon
Subject: Execute immediate performance varies between clients
Lines: 28
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4bc6bd81@forums-1-dub>
Date: 15 Apr 2010 00:17:21 -0700
X-Trace: forums-1-dub 1271315841 10.22.241.152 (15 Apr 2010 00:17:21 -0700)
X-Original-Trace: 15 Apr 2010 00:17:21 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2473
Article PK: 21713

Hi,

I have found the system runs really fast on my machine and one other but 3
other machines I test with run really slow.
I have traced this down to the execute immediate statement.
On the fast machines 10 execute statements shows 0 second to run but on the
other machines it says 4 seconds.
Any ideas on why this would be happening?

I am using a SQL Server 2000 database with connection DBMS = "SNC SQL Native
Client(OLE DB)"

The statement I have been testing with below.

integer i
string ls_sql
time lt_time
lt_time = now()
for i = 1 to 10
ls_sql = "DELETE FROM dba.dslock WHERE table_name = 'A' AND column_name =
'B' "
EXECUTE IMMEDIATE :ls_sql;
COMMIT;
next
messagebox("time taken",string(SecondsAfter ( lt_time, now() )))


Michael K Posted on 2010-04-20 01:15:48.0Z
Reply-To: "Michael K" <michael.kench@stiearc.com.au>
From: "Michael K" <michael.kench@stiearc.com.au>
Newsgroups: sybase.public.appeon
References: <4bc6bd81@forums-1-dub>
In-Reply-To: <4bc6bd81@forums-1-dub>
Subject: Re: Execute immediate performance varies between clients
Lines: 33
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1"; reply-type=response
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Windows Mail 6.0.6002.18005
X-MimeOLE: Produced By Microsoft MimeOLE V6.0.6002.18005
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4bcd0044$1@forums-1-dub>
Date: 19 Apr 2010 18:15:48 -0700
X-Trace: forums-1-dub 1271726148 10.22.241.152 (19 Apr 2010 18:15:48 -0700)
X-Original-Trace: 19 Apr 2010 18:15:48 -0700, vip152.sybase.com
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.appeon:2476
Article PK: 13451

The performance difference was due to the clients using Avast! antivirus.

"Michael K" <michael.kench@stiearc.com.au> wrote in message
news:4bc6bd81@forums-1-dub...
> Hi,
>
> I have found the system runs really fast on my machine and one other but 3
> other machines I test with run really slow.
> I have traced this down to the execute immediate statement.
> On the fast machines 10 execute statements shows 0 second to run but on
> the other machines it says 4 seconds.
> Any ideas on why this would be happening?
>
> I am using a SQL Server 2000 database with connection DBMS = "SNC SQL
> Native Client(OLE DB)"
>
> The statement I have been testing with below.
>
> integer i
> string ls_sql
> time lt_time
> lt_time = now()
> for i = 1 to 10
> ls_sql = "DELETE FROM dba.dslock WHERE table_name = 'A' AND column_name =
> 'B' "
> EXECUTE IMMEDIATE :ls_sql;
> COMMIT;
> next
> messagebox("time taken",string(SecondsAfter ( lt_time, now() )))
>
>
>