Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

concerns using linked server -security. Expand / Collapse
Author
Message
Posted Friday, April 26, 2013 4:47 PM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Wednesday, December 10, 2014 10:06 AM
Points: 1,792, Visits: 3,261
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,

Post #1447202
Posted Friday, April 26, 2013 5:57 PM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Yesterday @ 6:07 PM
Points: 1,816, Visits: 5,912
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


  • MMGrid Addin
  • MMNose Addin


  • 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

  • Post #1447206
    Posted Friday, April 26, 2013 6:18 PM
    SSCommitted

    SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

    Group: General Forum Members
    Last Login: Wednesday, December 10, 2014 10:06 AM
    Points: 1,792, Visits: 3,261
    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
    Post #1447208
    Posted Sunday, April 28, 2013 8:40 PM
    Old Hand

    Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

    Group: General Forum Members
    Last Login: Monday, December 1, 2014 3:42 PM
    Points: 364, Visits: 386
    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.

    Post #1447356
    « Prev Topic | Next Topic »

    Add to briefcase

    Permissions Expand / Collapse