OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
From: ArunKumar (akumarOMNESYSINDIA.COM)
Date: Tue Feb 26 2002 - 22:28:22 CST

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

    Is it absolutely necessary that u call it from inside a SP?
    Simply executing the call once as an ad hoc SQL
    statement should also do the wrk right ?

    arun

    ----- Original Message -----
    From: "Sorin Rojea" <SorinRIQ-L.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Monday, February 25, 2002 8:37 PM
    Subject: Re: COM+ - Getting Started...

    Calling SET TRANSACTION ISOLATION LEVEL from a stored procedure will set
    a new isolation level(default is SERIALIZABLE in COM+),
    but only on the connection which executes the SP.

    Other connection may still run under SERIALIZABLE level.

    Regards,
    Sorin

    -----Original Message-----
    From: ArunKumar [mailto:akumarOMNESYSINDIA.COM]
    Sent: Sunday, February 24, 2002 11:49 PM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM+ - Getting Started...

    Sorin Rojea wrote -

    "if a transactional COM+ component executes a store procedure that has
    BEGIN TRANS...COMMIT TRANS
    it just simply ignore the SQL-TRANSACT code. So you'll not end up having
    nested transactions."

    What happens if somebody executes or call SET TRANSACTION LEVEL
    isnide the component - wouldnt that affect the transaction level ?

    ----- Original Message -----
    From: "Sorin Rojea" <SorinRIQ-L.COM>
    To: <DCOMDISCUSS.MICROSOFT.COM>
    Sent: Thursday, February 21, 2002 3:46 AM
    Subject: Re: COM+ - Getting Started...

    some comments inline

    -----Original Message-----
    From: Peter Foreman [mailto:peter_foremanYAHOO.COM]
    Sent: Wednesday, February 20, 2002 4:48 AM
    To: DCOMDISCUSS.MICROSOFT.COM
    Subject: Re: COM+ - Getting Started...

    --- Chris Lawton <clawtonCSC.COM> wrote:
    > I've got code that does SQL as such...
    >
    > BEGIN TRANSACTION
    > Do some SQL updates, etc...
    > COMMIT TRANSACTION (or ROLLBACK)
    >
    > So my question is, seeing that COM+ supports transactions, the COM+
    > transactions don't replace
    > the SQL Server transactions, do they? If so, durring our port, I'll
    need
    > to make methods that
    > are wholly contained within a transaction if it needs one. True?

    >>>COM+ transactions are an alternative to codified transactions such as
    your example.

    if a transactional COM+ component executes a store procedure that has
    BEGIN TRANS...COMMIT TRANS
    it just simply ignore the SQL-TRANSACT code. So you'll not end up having
    nested transactions.

    > But how do I write a method to not use a transaction. (Or...is there
    > something you write to tell a
    > method to begin/commit a transaction.)

    >>>In COM+ just mark it as not requiring a transaction. This can be
    done in the idl file in C++, and
    >>>in the properties windows in VB, both of which compile the attribute
    into the associated typelib.
    >>>Also the COM+ explorer admin console shows this and allows
    modification, although it is better to
    >>>set it up in code.

    If you want some of the methods execute transactions and some of them
    not, you have to mark the component
    disable transactions, and manually enlist(or start) the ADO or OLEDB
    connection in the transaction.

    > OR...are the COM+ trasactions there to provide a transaction service
    for
    > resources that don't normally
    > have one, such as files? (and I don't use the COM+ transaction service
    for
    > SQL?)

    >>>No.

    Actually there is a way to include nontransactional operations(file
    access, registry, etc.).
    You have to use the Compensating Resource Manager(CRM) -- search in MSDN
    for Compensating Resource Manager.
    You can also find a good example on MSDN magazine, but I can't remember
    wich number.

    > Lastly, any general advice on where to concentrate study?
    Transactions?
    > Isolation? Apartments?
    > (I'm pretty familiar with DCOM and its model, but this will be my
    first
    > work with MTS and SQL Server from
    > a COM+ object)

    >>>Get hands on with a few bit of trial code before starting your port.

    Transactions?
    Yes
    Isolation?
    Yes
    Database locks?
    Yes
    ADO and OLEDB?
    Yes, again.
    Apartments?
    Not really. The most scalable model is Apartment, so I suggest use that
    one.

    Tim Ewald's book is one of the best, so keep use it as a reference.
    You might want to try another very good book "COM+ and .NET" by Juval
    Lovy.

    Best of luck,
    Sorin

    ----------------------------------------------------------------
    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

    ----------------------------------------------------------------
    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