| |
|
Syteview gives you the tools you need to replicate your data from a
Progress database server to a Microsoft SQL Server
in real-time. This Microsoft SQL Server is used to isolate and protect your Progress server from the
internet while at the same time taking almost all of the processing load of publishing the data off of the Progress server
so it can continue with its other tasks unimpeded.
By replicating your data to a second database server Syteview allows you to use several
networking techniques to isolate your Progress server. First, you can subnet your network and place the Progress
server on a subnet that is inaccessible from the internet. Second, you can place a firewall between your Progress
server and your SQL Server and filter out any packets from the internet side that do not originate from your SQL Server.
Third, you can add a second network adapter to your Progress server and use it to connect to the SQL Server with a
non-routable network protocol such as NetBEUI. By using a non-routable protocol to connect the two servers you
make sure that any attempts to reach your Progress server will not make it past the first router (see
Fig. 1).
Another benefit of using the Microsoft SQL Server to publish your data is to protect your
Progress database server from your legitimate users. If you give your users the ability to access your Progress
server via an ODBC connection you run the risk of a user initiaing a query that will use all of your server's CPU cycles
for the rest of the day. End-users simply do not know what they are doing, or in this case, what they are asking.
What seems to them to be a reasonable request could easily consume all of your Progress server's resources, leaving none
for your other users. Syteview overcomes this problem by using Stored Procedures on the SQL Server to retrieve
your data. These Stored Procedures are written with speed and economy in mind, and include upper limits on the
amount of server resources they will consume. These limits will prevent any single user
from monopolizing your server.
See Syteview Design and Architecture for a more
involved discussion of isolating and protecting your Progress database server.
|
|
|
