Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


concerns using linked server -security.


concerns using linked server -security.

Author
Message
sqlfriends
sqlfriends
SSCrazy
SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

Group: General Forum Members
Points: 2491 Visits: 3867
We are designing of an application that using backend SQL database. When records are inserted into a SQL table, we also wanted to update records in an oracle database. The plan is to using linked server in SQL , and create an trigger when SQL server records are updated, then Oracle will be updated too.

We don't use linked servers in our environment for Security reasons, but if it is needed we have to go this route. Any recommendations for security of linked server?

Thanks,
mister.magoo
mister.magoo
SSCrazy
SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)SSCrazy (2.7K reputation)

Group: General Forum Members
Points: 2653 Visits: 7851
Not an answer about linked servers, more about triggers...

Please don't use a trigger for this, make all your transactions through stored procedures and have that update the Oracle server, or even better have the stored procedure write to a message queue and have a separate process updating Oracle from that queue...

MM


select geometry::STGeomFromWKB(0x0106000000020000000103000000010000000B0000001000000000000840000000000000003DD8CCCCCCCCCC0840000000000000003DD8CCCCCCCCCC08408014AE47E17AFC3F040000000000104000CDCCCCCCCCEC3F9C999999999913408014AE47E17AFC3F9C99999999991340000000000000003D0000000000001440000000000000003D000000000000144000000000000000400400000000001040000000000000F03F100000000000084000000000000000401000000000000840000000000000003D0103000000010000000B000000000000000000143D000000000000003D009E99999999B93F000000000000003D009E99999999B93F8014AE47E17AFC3F400000000000F03F00CDCCCCCCCCEC3FA06666666666FE3F8014AE47E17AFC3FA06666666666FE3F000000000000003D1800000000000040000000000000003D18000000000000400000000000000040400000000000F03F000000000000F03F000000000000143D0000000000000040000000000000143D000000000000003D, 0);




  • Forum Etiquette: How to post Reporting Services problems
  • Forum Etiquette: How to post data/code on a forum to get the best help - by Jeff Moden
  • How to Post Performance Problems - by Gail Shaw

  • sqlfriends
    sqlfriends
    SSCrazy
    SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)SSCrazy (2.5K reputation)

    Group: General Forum Members
    Points: 2491 Visits: 3867
    mister.magoo (4/26/2013)
    Not an answer about linked servers, more about triggers...

    Please don't use a trigger for this, make all your transactions through stored procedures and have that update the Oracle server, or even better have the stored procedure write to a message queue and have a separate process updating Oracle from that queue...



    Thanks, could you help to explain why using trigger is not recommended?

    What is a message queque, is it SQL server or Oracle related?

    Thanks
    Mansfield
    Mansfield
    Old Hand
    Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)Old Hand (384 reputation)

    Group: General Forum Members
    Points: 384 Visits: 394
    All code inside a table trigger is within the scope of the transaction that started the trigger. Fine in theory, in practice especially involving queries to other servers will cause performance problems as the originating query cannot continue until everything has synchronously completed.

    A message queue is a generic programming construct. (Refer to the Wikipedia article) For example, Service Broker is an implementation of a message queue system within SQL Server.

    In this case using a message queue will allow the inter-database updates to be done asynchronously.
    Go


    Permissions

    You can't post new topics.
    You can't post topic replies.
    You can't post new polls.
    You can't post replies to polls.
    You can't edit your own topics.
    You can't delete your own topics.
    You can't edit other topics.
    You can't delete other topics.
    You can't edit your own posts.
    You can't edit other posts.
    You can't delete your own posts.
    You can't delete other posts.
    You can't post events.
    You can't edit your own events.
    You can't edit other events.
    You can't delete your own events.
    You can't delete other events.
    You can't send private messages.
    You can't send emails.
    You can read topics.
    You can't vote in polls.
    You can't upload attachments.
    You can download attachments.
    You can't post HTML code.
    You can't edit HTML code.
    You can't post IFCode.
    You can't post JavaScript.
    You can post emoticons.
    You can't post or upload images.

    Select a forum

































































































































































    SQLServerCentral


    Search