Plus, what happens to those
handfuls of people who don??™t receive the directive to log out and back in? What if the registry
update fails for some unknown reason? Those users get left out, and the result will
most likely be an angry help desk and a significant amount of support work??”again, not
very efficient.
If your client machine is a middle tier through which all real clients get routed, then
changing the client DSN can be a feasible technique. For a single server acting as the
middle tier (whether it??™s an application server or a Web server), changing that server??™s
DSN will work nicely with little interruption to the end client. Even if you have a farm of
servers acting as one, it??™s still easier to update a farm than every single client. However,
you must be diligent in your process and in your documentation; updating a server farm
and missing a single server can create the same support nightmare that a misbehaving
registry update can cause.
THE CONFUSION OF CONFIGURING A DSN
One of my biggest pet peeves with all products is terminology, or more precisely, outdated or misleading
terminology.
Pages:
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326