Reliability & Efficiency of Database links for far located remote databases

[vdevnani]

Hello..
My current architecture consists of a client and server; which are located quite near to each other.....and i am using database links to retrieve / send data from or to the server.
for eg. if i want to select rows from a table in the client database i use
" SELECT * FROM NAMES@DB_LINK_FOR_1 "

But now the distance between the client and server has increased hugely. Assume the distance to be of some 30 Kilometers. So how reliable are the database links for such a long distance. I have an alternative of using XML files transfer by coding in C#.NET 2005. But somehow I am not convinced with the security of XML files and due to some other dependencies on Microsoft Visual Studio.NET .

Please suggest something! Help!

[amitpatel66]

Hello..
My current architecture consists of a client and server; which are located quite near to each other.....and i am using database links to retrieve / send data from or to the server.
for eg. if i want to select rows from a table in the client database i use
" SELECT * FROM NAMES@DB_LINK_FOR_1 "

But now the distance between the client and server has increased hugely. Assume the distance to be of some 30 Kilometers. So how reliable are the database links for such a long distance. I have an alternative of using XML files transfer by coding in C#.NET 2005. But somehow I am not convinced with the security of XML files and due to some other dependencies on Microsoft Visual Studio.NET .

Please suggest something! Help!

For what reason you are going select the data from that database?
If it is got to be one time process where you need to select data once, then you need not worry about reliability. In case if you are going to communicate with the DB so often, then you can create a private database LINK for your user and then use them. They are ofcurse reliable but again it all depends on the availibility of that database

[debasisdas]

So far as the client and server are connect via WAN or something else ,you need not bother about the distance. That is not a barrier for the Database links.

[vdevnani]

So far as the client and server are connect via WAN or something else ,you need not bother about the distance. That is not a barrier for the Database links.

Hi Amit n Debasis..
thanks 4 d replies guys..

now....
select statement was just an example....actually d server keeps on updating and inserting data on the client database...so yes..it is a quite frequent process...n moreover...i m also pulling the data from clients...so its bidirectional..

about the network....i guess its a WLAN or VSAT or VPN ....anyhow it would surely be a private network....

so in case of multiple clients...what i understand the steps would be:
1. Open connection for client_1 with DBLINK_1
2. Perform operations
3. Close connection
4. Open connection for client_2 with DBLINK_2
5. Perform operations
6. Close connection
---
---
and so on..

as i said the data transfer is bidirectional.....so what do you guys suggest...for maximum of 15-20 client databases...located at a long distance from server database..connected through some network (assuming network is ideally up)....would the database links be an optimal solution..?

[amitpatel66]

Yes the DBLINKS will be reliable and efficient to use for any number of client connections. In case if there is not much security concerns, then you can go for Public DBLINK which can be used by all the users of the DB to get the data from that different database. Else you need to go for private DB LINK one for each user respectively. And again you should remember proper privileges to be GRANTED to the user, on different objects of that database that you are going to use.

[vdevnani]

Okkk...

Great then..!

Thanks to all u guys...!

I'll just check it out for the distances n later on i'll post a reply...

Thanks again!