Re: MTS & Oracle 8i

With SQL Server Query Analyzer the commits are implicit (I personally think this is a BAD thing, but then MS didn't ask me...). However, SS does support transactions - and not just those manages by DTC, which require a 2-phase commit.

If you are seeing ORA-00000 errors then there should be Oracle trace files being generated on the MTS server. These will be in the format {dist_trans_id}.trc, where the distributed transaction identifier is a long sequence that looks like a GUID. Examining these will point to the root cause of the problem.

I hope you aren't paying MS Consulting Services for their opinions, as in general VB COM objects under MTS will not be "more efficient" that PL/SQL procedures. There could be specific cases where this would be true, but this would not be the norm.

Also, MS is not telling you about the scalability issues that still exist with Oracle and Microsoft Transaction Server or COM+. You cannot code around the limitations using VB, though there are techniques that can be applied (via pooled objects) with COM+ Services in Windows 2000.

I'm not trying to tell you that the use of MTS / COM+ is a bad thing, because there are advantages that can be achieved by this framework. However, it isn't a "one size fits all" strategy - even though many of the people implementing solutions based on the framework think it is. This opinion is generally due to working on small-scale projects, which fails to expose the limitations.

Mike

"Rod Sherer" <rsherer_at_prescientsystems.com> wrote in message news:38fda330_at_news.deniz.com...
> The problem is, I don't know enough about the Microsoft Transaction Server
> (not to be confused with Oracle's MTS) or SQL Server. When using the SQL
> Server Query Analyser, I don't even see that commits and rollbacks even
> exist like they do in Oracle. This is why I thought they set things up
 using
> MTS to control the transactions.
>
> I still haven't seen the archetecture work properly though, especially not
> against Oracle. Even with v8.0.5.x, there are issues with ORA-00000 when
> letting the transaction server control the transaction.
>
> And they did say that using VB COM objects with MTS would be more
 efficient
> than our existing code in PL/SQL. Again, I haven't seen the proof in the
> pudding yet. So far things have been considerably slower (seen in unit
> testing), but I don't know if this is the technology or the implementation
> at this point.
Received on Fri Apr 21 2000 - 00:00:00 CDT