Discussion Locked

Enterprise (WAN/LAN) deployment

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I wrote Visual Basic 6 application with MS SQL 2000 Server Backend. It runs well in the test environment on small Office LAN.
What all do I need to do or watch out for when I begin to deploy the application enterprise wide (LAN/WAN) environment?The databse will be centralized on the current SQL 2000 server and will not be distributed.

5 replies

by estebandelatorre

SQL and VB is the best mix for a WAn application.
What I recommened to look first is:
1. The amount of data to be transferred between client and server. If your app. involves graphics, images, and so on, the performance could be degraded, and a WEB application + SQL could be the solution, due the optimization cache structure.
2.- Timeouts: Be sure to have odbc time outs properly setting (api way) and reconnect options should be included into the code.
3.- Due to the lost connection / timeout issues, is recommended that every operation to the sql databases should be done using store procedures. You may be able to roll back all the transaction if something fails.
4.- If the apllication will be released for more than 100 users, watch carefull the sql memory usage.

Hope it helps!

by stillatit

Here are a few things that will bite you.

Be very aware of how much information you are really requesting. For example, if you have a large number of pull-down lists on a screen, populated by SQL statements, the screen will still load quickly on a LAN. It may be horribly slow when you are on a slower wan, especially as the number of users goes up.

Consider that your test database is small, and your production database will be much bigger. A query that does not use an index still runs faston a small database. It will kill you on a large database.

In the same way, using a grid to select a record works well on a small database. It works poorly when you try to add thousands of lines to the grid.

Think about WHERE a selection will resolve. Hopefully, your server will do your filtering, and return only the records you need. If you do it wrong, you might read all the records across the wan, and try to select records locally on each PC. (Ouch!)

Good luck.

This discussion is closed to new replies.