September 15, 2006 at 7:34 am
I am working on an asp.net application that uses SQL server as it's main database. However there are times I am going to need to connect to an oracle database as well and as of now it is not looking like I am going to be given permissions to create or execute stored procedures.
I am a little worried about using inline sql so I was thinking about using sql server stored procedures to pull the query out of the DB and pass the sql server the variables for the query and have it simply return the whole query put together then send that to oracle.
I guess I am wondering how people feel about this?
We have the oracle db set up as a linked server on the sql server however no one else that uses it from there has the right to update the DB so this linked server connection will not do everyhting I need it to do.
September 18, 2006 at 3:51 am
To me it sounds like you should use two connection strings in your application. One to the SQL Server and one to the Oracle Server. In my opinion you don't have to worry about inline code. It doesn't harm the performance and can sometimes even be easier to use in your code! Make sure you use a data layer in your app though.
I don't think you should bother making some kind of query-builder (or a single table with Oracle-queries) in SQL Server. What's the point of that? Why are you worried about inline sql?
September 21, 2006 at 7:29 am
we have some people at my company that like to see how far they can "hack" something - I would like to prevent that as much as possible.
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply