In most cases a SQL Anywhere server without a database is a singularly useless entity. A High Availability Arbiter server, however, is an example of a server-without-a-database that performs a singularly useful role... why, then, does it not feel that way to a database administrator?
Sure, you can use ISQL to connect to an arbiter server using the phantom "utility_db"...
but you can't DO much except ask "What version of the software is running?"...
You can't even do something as simple as "Show me all the SET options"...
Sybase Central also lets you connect to an arbiter server, but it too screams "Keep your hands to yourself!" when you ask for the simplest thing...
The problem is, SQL Anywhere needs a database to do anything at all... the difference between "empty database" and "no database at all" is vast.
Please, Mr. SQL Anywhere, give the arbiter a database!
Then the administrator can check on the arbiter's health and status, beyond the basic question "Can I connect?"
Maybe even check on the performance of the arbiter, who knows? You can't do anything without a database.
1 comment:
Why not just run a small database on that server? In v16 and later versions of v12.0.1, the arbiter can also be a copy node for the database for which it is an arbiter.
Post a Comment