Working with a read-only database - SQL Server

• christina.constantinou

  Old Hand

  Points: 302

  More actions

  March 7, 2013 at 5:48 am

  #394330

  Hey,

  In preparation for the building of a new application in my organisation, I've come up against a bit of a brick wall when working across multiple databases.

  We are developing a 3rd party application that needs to send information to the accounting application database. Once it gets there, it needs to be calculated and returned to the 3rd party application.

  Our accounting application has a read only database for security purposes. We are able to use the front end to carry out day to day accounting, and we are also able to pass information into the system using an ETL tool specific to the application i.e. we cannot write directly to this database.

  We have considered using SSIS for this, but are concerned about the performance implications.

  Would we be in a better position if we had a connection to the accounting database to display the current information (i.e. the balance of an account), and used our 3rd party front end application to carry out the same calculation as the accounting software would do, while the accounting software is awaiting the relevant data?

  Both of these databases SQL server 2008R2. The front end application is written in .NET, and the accounting software is Progress based.

  Any advice would be welcomed!

  Thanks

  Cris