1

Topic: Job and transaction

Good afternoon.
There was a task to launch process of generation of "codes". It is possible to launch process that one million such codes, operation heavy enough created and each code is record in some tables. Selected for this purpose  that to itself there by hours it was twisted and did not hinder. The configuration  is transited, thanks . The new problem is transaction in .
How much understood, and checked up , together with  transaction starts. It is necessary each successful pack from 1.000 codes , everyone it is erratic  to roll away the code since it is record in some tables.
For the notification about the status  procedure which will be written to write down the data in the table through loopback, such independent transaction.
Actually a problem with packs and rollbacks:
Packs. If I start the transaction that all it expects  exterior transaction, i.e. I do not see given by hours yet all does not end .   but it is natural counters of transaction do not converge. I suspect that transaction log all this time will swell without physical ,  are ignored.
Rollbacks. Here on savepoint likely it is possible. Whether whether loads strongly the server creation savepoint for each iteration and correct is the approach.

2

Re: Job and transaction

mezzanine wrote:

How much understood, and checked up , together with  transaction starts.

Is not present,  - whether it is system of start of that  under the schedule or the requirement. For example, periodically to consider exchange rates from site  or to make  bases.
You create transactions, or they form automatically in that program which is launched by it .

mezzanine wrote:

Packs. If I start the transaction that all it expects  exterior transaction, i.e. I do not see given by hours yet all does not end .   but it is natural counters of transaction do not converge. I suspect that transaction log all this time will swell without physical ,  are ignored.
Rollbacks. Here on savepoint likely it is possible. Whether whether loads strongly the server creation savepoint for each iteration and correct is the approach.

you need to fulfill all in transaction? For example, what it would be possible to roll away all? Then do the general transaction, any savepoint do not help. The broad gull will grow.
Transactions are not necessary? Do not do them besides any savepoint are not necessary. The broad gull will not grow.

3

Re: Job and transaction

mezzanine wrote:

Kommichu  but is natural counters of transaction do not converge.

It is necessary to do so much commit, how many begin tran was before.
For implicitly open transaction (I doubt that at you this case) enough one commit.

4

Re: Job and transaction

wrote:

the New problem is transaction in .

You would not need to write the code in steps of jobs, and to create procedures and to cause already procedures in a step.