DevX Home    Today's Headlines   Articles Archive   Tip Bank   Forums   

Results 1 to 3 of 3

Thread: Accessing a DB on another domain

  1. #1
    john Guest

    Accessing a DB on another domain


    We have an Web app using ASP to call and instantiate MTS COM components, which
    in turn will access a MS SQL DB on a different domain through OLE DB. We
    have found that the performance is bad, and cannot think of another way to
    set up our environment.

    The DB must remain where it is, but the app/com components can be moved.

    Does anybody have any ideas?

    Thanks in advance,

    John.

  2. #2
    Martin Rydman Guest

    RE: Accessing a DB on another domain

    Are you sure it's the setup that causes the performance hit? There are so
    many ways you can screw up performance...

    /Martin
    john <jedsid@home.com> skrev i
    diskussionsgruppsmeddelandet:39c67383$1@news.devx.com...
    >
    > We have an Web app using ASP to call and instantiate MTS COM components,

    which
    > in turn will access a MS SQL DB on a different domain through OLE DB. We
    > have found that the performance is bad, and cannot think of another way to
    > set up our environment.
    >
    > The DB must remain where it is, but the app/com components can be moved.
    >
    > Does anybody have any ideas?
    >
    > Thanks in advance,
    >
    > John.




  3. #3
    John Guest

    RE: Accessing a DB on another domain


    "Martin Rydman" <martin.rydman@telia.com> wrote:
    >Are you sure it's the setup that causes the performance hit? There are so
    >many ways you can screw up performance...
    >
    >/Martin


    Well, yes...our major limitation is the bandwidth between the two domains
    (one domain with the mts components and the other with the database). We
    have done some tests and have found that there is a lot of traffic on this
    line being sent back and forth. A fair amount of that traffic is 'Business
    logic' related (i.e. verify if account exists on database, if so, continue,
    etc.). However, a fair amount can be attributed to system messaging, etc.
    We're looking for alternative setups. At this point, we are trying to install
    the components locally into the database domain, and refenece them as remote
    components. The problem with this is that we are decentralizing the components
    and any future expansions to other databases would require the same components
    installed locally, etc. Any ideas/suggestions would be greatly appreciated!

    Thanks,

    John.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
HTML5 Development Center
 
 
FAQ
Latest Articles
Java
.NET
XML
Database
Enterprise
Questions? Contact us.
C++
Web Development
Wireless
Latest Tips
Open Source


   Development Centers

   -- Android Development Center
   -- Cloud Development Project Center
   -- HTML5 Development Center
   -- Windows Mobile Development Center