Re: Locking Info
- From: "ashish" <ashishg@xxxxxxxxxxxxxx>
- Date: 21 Jul 2005 19:49:31 -0700
This probably is expected behaviour.
You may be aware that from ASE 12.5.0.3, multiple temporary databases
are available to deal with such concurrency problems.
If upgrading is not an option, you could try to distribute the creation
of your own temporary tables in explicitly created databases for this
purpose ... Then your temp tables cannot be of the form #table1. They
will need to be of the form user_tempdb1..table1.
This surely is an awkward solution. This will not benefit concurrency
problems related to internally generated temporary tables (such as
worktables generated for sorting).
Regards,
Ashish
.
- Follow-Ups:
- Re: Locking Info
- From: su
- Re: Locking Info
- References:
- Locking Info
- From: su
- Locking Info
- Prev by Date: Locking Info
- Next by Date: Re: What is better? One database vs multiple databases under one engine.
- Previous by thread: Locking Info
- Next by thread: Re: Locking Info
- Index(es):