OS: WinXP sp3 32bit; SQL Anywhere: 11.0.1.2701

When reload DB, if table have GLOBAL autoincrement primary key, then time to create the trigger too long (depend of table width and count of records). Workaround: defining triggers in another file.

This is normal behavior?

case# 11701261

asked 17 Nov '11, 23:32

Marsel's gravatar image

Marsel
185256
accept rate: 33%

Could you please tell more details?

Is the trigger part of the reload.sql file? How do you measure the time it takes for the CREATE TRIGGER statement?

(19 Nov '11, 08:25) Volker Barth

Is the trigger part of the reload.sql file? yes

How do you measure the time it takes for the CREATE TRIGGER statement?

CREATE VARIABLE aTime timestamp go

set aTime = current timestamp go

create trigger test_trigger1 before update order 1 on dba.test <skip>

print string('create test_trigger1 seconds: ', DATEDIFF(second, aTime, current timestamp)) go

I can't attach file. I need more reputation points :) (>100)

(19 Nov '11, 10:29) Marsel
Be the first one to answer this question!
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×137
×14

question asked: 17 Nov '11, 23:32

question was seen: 1,109 times

last updated: 19 Nov '11, 10:29