For example, look at the number of features that use the term snapshot in SQL Server
2005: snapshot isolation, database snapshots, snapshot replication, Snapshot Agent. These kinds of
less-than-distinct naming conventions lead to more confusion with clients than I care to deal with.
My biggest terminology annoyance is the name of the icon within the administrative tools for configuring
DSNs: Data Sources (ODBC). It still appears that way with Windows XP and Windows Server
2003. I often have to dispel the assumption that whenever you add something, you??™re using ODBC. Not
true. You??™re creating a DSN for some sort of database connection. It could be ODBC. It could be ODBC
for OLE DB. It could be the Oracle OLE DB driver for Oracle. It could be SQL Server Native Client (lovingly
termed SNAC). Whatever database networking clients are installed on that machine will show up
when creating a DSN. Rarely will they actual go through an ODBC layer.
Rename the Server and Change the IP Address
If you have no middle-tier application layer, the simplest method for manual failover is to
rename the standby server, change its IP address to what you??™ve been using for the principal
server, and reboot.
Pages:
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327