OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: Liviu Anca (LiviuEON.RO)
Date: Fri Mar 08 2002 - 08:39:25 CST

  • Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

    *This message was transferred with a trial version of CommuniGate(tm) Pro*
    Some comments...

    Of course, using OLEDB Provider for SQL Server (SQLOLEDB) is more efficient
    than using OLEDB Provider for ODBC and ODBC Driver for SQL Server, but since
    version 3.0 ODBC knows connection pooling, so, I think it's not a provider
    problem.
    Using "with (nolock)" is less restrictive than not using locking hints at
    all (assuming the default isolation level), so, it's not a locking problem.
    A deadlock condition is explicitly detected and reported by SQL Server
    (unless it's not "BUG: 1205 - Deadlock Situation Not Detected by SQL Server"
    :), Q239753, as Phil already mentioned).
    Maybe you should try without any transaction support and see what's
    happening.

    Liviu Anca

    -----Original Message-----
    From: Distributed COM-Based Code [mailto:DCOMDISCUSS.MICROSOFT.COM]On
    Behalf Of Phillip Allan-Harding
    Sent: Friday, March 08, 2002 2:07 PM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM+ Transactions
    Importance: High

    *This message was transferred with a trial version of CommuniGate(tm) Pro*
    This is all but impossible to diagnose over the wire, but it sounds like
    it could have something to do with locking.

    * See MSDN articles Q290486, Q239753
    * Try testing using a single instance of your other component/DBComp on
    a dev machine
    * Remove the Locking Hint NOLOCK from your SP's
    * Use the default transaction isolation level of READ COMMITTED
    * Use the OLEDB provider and ensure that the connection pooling service
    is enabled
            the OLEDB_SERVICES value should be 0xffffffff at key

    HKEY_LOCAL_MACHINE\SOFTWARE\Classes\CLSID\{0C7FF16C-38E3-11d0-97AB-00C04
    FC2AD98}

    Phil Allan-Harding.
    Graphicboost Development
    Tel: +44(0) 161 980 4136
    Mobile: +44(0) 7778 561119
    Email: developergraphicboost.com
    Web: http://www.graphicboost.com

    -----Original Message-----
    From: Linson Zacharia [mailto:linsonBGL.VSNL.NET.IN]
    Sent: Friday, 08 March 2002 02:39
    Subject: Re: COM+ Transactions

    The DBComp, Object pooling, JITA enabled
    I'm using ADO
    There are certain methods in DBComp, in each method I'm creating
    connection and in the end releasing it .. The sp is updating certain
    fields in some other tables ..

    TIA,
    Linz

    ----- Original Message -----
    From: "Phillip Allan-Harding" <philGRAPHICBOOST.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Thursday, March 07, 2002 5:01 PM
    Subject: Re: COM+ Transactions

    > Can you describe your DBComp component a bit more
    >
    > * what are it's activation characteristics (Pooling,JITA)
    > * what DB access technology are you using (OLEDB,ADO)
    > * when do you open/close your DB connection
    > * what is your stored procedure doing
    >
    > Phil Allan-Harding.
    > Graphicboost Development
    > Tel: +44(0) 161 980 4136
    > Mobile: +44(0) 7778 561119
    > Email: developergraphicboost.com
    > Web: http://www.graphicboost.com
    >
    >
    > -----Original Message-----
    > From: Linson Zacharia [mailto:linsonBGL.VSNL.NET.IN]
    > Sent: Thursday, 07 March 2002 03:20
    > Subject: COM+ Transactions
    >
    >
    > Hi All,
    >
    > Env: VC++ 6.0/ATL/sp5, Win2K/sp1, SQL 7.0/sp2, ADO 2.6/sp1
    >
    >
    > There are two components deployed in COM+, one which requires
    > transaction and another component (DBComp) which supports transaction.

    > All the DB oprerations are going through this DBComp. The first
    > component uses the DBComp to execute a stored procedure and its
    > waiting for up to the transaction timeout and its coming out giving
    > error "[Microsoft][ODBC SQL Server Driver][SQL Server]Distributed
    > transaction completed. Either enlist this session in a new transaction

    > or the NULL transaction." In the stored procedure everywhere I'm using

    > the "with (nolock)".
    >
    > Anybody can help me in this ?
    >
    > TIA,
    > Linz
    >
    > ----------------------------------------------------------------
    > Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    > contains important info. Save time, search the archives at
    > http://discuss.microsoft.com/archives/index.html . To unsubscribe,
    > mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM
    >

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM

    ----------------------------------------------------------------
    Users Guide http://discuss.microsoft.com/archives/mailfaq.asp
    contains important info. Save time, search the archives at
    http://discuss.microsoft.com/archives/index.html .
    To unsubscribe, mailto:DCOM-signoff-requestDISCUSS.MICROSOFT.COM