Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>IMO easiest way is to </p> <ul> <li>Add Return value to remote proc.</li> <li>Wrap remote proc into transaction and try catch (inside remote proc). If error happened return false. </li> <li>On local stored proc if false, simply do not continue. </li> </ul> <p>I also fail to understand the reason behind multiple BEGIN TRANS / COMMIT in the local proc. I mean if this is month end rollup, shuldn't this be one big transaction rather than a bunch of small? Otherwise your trans 1 and 2 may commit successfully, but 3 will fail and that's that. </p> <p>Names are made up ofc:</p> <pre><code> CREATE PROC [remote].db.REMOTE_PROC ( @return_value int output ) AS BEGIN SET XACT_ABORT ON; BEGIN TRY BEGIN TRANS ... do stuff ... set @return_value = 1; COMMIT; END TRY BEGIN CATCH set @return_value = 0; END CATCH END </code></pre> <p>and the local proc</p> <pre><code> CREATE PROC [local].db.[monthlyRollUp] AS BEGIN SET XACT_ABORT ON; declare @ret int; EXECUTE [remote].dbo.REMOTE_PROC @return_value = @ret OUTPUT; IF @ret = 0 PRINT 'ERROR :(' RETURN END IF BEGIN TRANS -- one big transaction here EXEC [LOCAL].[DB].[table].[sp1]; EXEC [LOCAL].[DB].[table].[sp2]; EXEC [LOCAL].[DB].[table].[sp3]; EXEC [LOCAL].[DB].[table].[sp4]; COMMIT; END; </code></pre> <p>afair [remote].dbo.REMOTE_PROC runs its own transaction space, and returns 1 if successful. Local proc, checks the return value and decides whether to proceed or not. </p> <p>sp1 sp2 sp3 and sp4 are all running in one single transactions, as having multiple transactions for each of them does not really make much sense to me. </p>
    singulars
    1. This table or related slice is empty.
    1. POReturn if remote stored procedure fails
      singulars
      1. PTQuestion
    1. PTAnswer
    1. USb0rg
    1. USb0rg
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. POReturn if remote stored procedure fails
      singulars
      1. PTQuestion
    1. This table or related slice is empty.
    1. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. PO
      1. This table or related slice is empty.
      1. VTUpMod
    1. COThe remote procedure cannot be wrapped into a transaction as support is not enabled for this. I do agree that the multiple small procedures should be combined.
      singulars
      1. PO
      1. USKermit
    2. COIt would help us greatly if you provide insight on overall system architecture, i.e. versions and manufacturer of both sql servers, method of connections used. I see oledb there, which does not make sense for ms sql, rather use Linked Server instead. Then put BEGIN TRANS / COMMIT inside remote stored proc, that way transaction is local to the Remote server. That requirement is unclear either. You can also program two phased commit on both servers, or you can setup MS DTC and distributed transactions between both servers.
      singulars
      1. PO
      1. USb0rg
    3. COI'll update with further specs. As a previous answer suggested and I replied, I'm hesitant to implement a DTC since it's being deprecated.
      singulars
      1. PO
      1. USKermit
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload