Posted by: F R Bhote
The isolation level is always RL. It's all over the audit.
To generate IDs, we use the method described by Lalwani:
Set sSelectId = 'SELECT S_ID_NO INTO :nNo FROM SYSADM.S_ID WHERE S_ID_DATE
Set sUpdateId = 'UPDATE SYSADM.S_ID SET S_ID_NO = S_ID_NO + 1 WHERE
S_ID_DATE = :dfDate'
If NOT ( SqlExecute( hSqlUpdId ) AND fnExists( hSqlSelId ) AND SqlExecute(
hSql ) )
Call SqlPrepareAndExecute( hSqlUpdId, sgRollback )
Call ErrorBox( sgSelIdErrMess )
where hSql is the Insert statement.
CREATE TABLE SYSADM.S_ID (
S_ID_NO DOUBLE PRECISION,
CREATE INDEX SYSADM.XS_ID_DATE ON SYSADM.S_ID(
I wonder if that index PCTFREE should be 99...
I would love to try SB 11, but after the (bad) experience I had with 9.0.1
PTF2, (the audit file was about 10 times the size) I would really like to
know if it is backward compatible without an unload. The database is up 24x7
and it takes about 5 hours to load. I'm still looking for a customer to flog
the unlimited user license to .
About 100 of our installations are multi-user and as Jim says, the End Task
by users is a major problem. We have given some of our users the dbconnects
program from the newsgroup to kill user connexions, but it's quite a
(While I type this, I have this on Instant Messenger:
raneventura1: hyper not working properly
raneventura1: very slow
raneventura1: have you checked y-day abc file ?)
Regarding the scenarios, let's take one from the audit I posted:
One guy is doing this:
INSERT INTO SYSADM.PARTY( P_CODE, P_NAME, P_DOB, P_ADDR1, P_ADDR2, P_ADDR3,
and another wants to select:
SELECT P_CODE FROM SYSADM.PARTY WHERE P_CAT = 'DZ'
the result of which is:
2 ROWS SELECTED
IN 0.02 SECONDS
INSERT INTO SYSADM.SAUDA
(S_DATE, S_NO, ...
where S_DATE is today's and S_NO goes from 1 upto something like 100,000.
The other guy is doing:
SELECT ... SUM( @DECODE( S_BILL_TYPE, 'd', S_RATE * S_QTY ) ), ...
FROM SYSADM.PARTY, SYSADM.SAUDA, ...
WHERE .... AND S_DATE BETWEEN :1 AND :2 AND...
where S_DATE is yesterday's or the day before's.
Regarding the 702/703, I've sent you a mail with a FAIL.SQL which is 3 MB
and too large to post on this group.
Case 927844 - Error 702 problems
While we are at it, there is another case regarding the ODBC driver "Case
927275 - Win CE And ODBC" which I do not think is solved as yet.
We all out here are very fond of SqlBase and don't see anyone having issues
on the management side. If you notice, all these years there have been 3
main things which everyone wants:
1. Concurrency (row-level locking),
2. Multi-processor support, and
F R Bhote
PS: SB8.5.0 PTF 4