|
The SQL Anywhere 11.0.1 Help is incorrect when it says the -xd option only applies to the network server... it applies to dbeng11 as well as dbsrv11. The -xd option (see Help here) was introduced in 11.0.1 to prevent the database server from becoming the default database server... for 99.99% of the world's SQL Anywhere installations, accidentally connecting to the wrong database server because "it's the default" or some other goofy reason is a clear and present danger, and anything one can do to prevent that from happening is a good idea. That's my opinion, anyway... the other 0.01%, I've never met, they may not exist. Testimonials: The SQL Anywhere Monitor that comes in the box uses -xd. Foxhound (now) uses -xd. You should too. It should be the default. Also highly recommended is -sb 0 to stop the engine from listening for UDP broadcasts ...but that's another topic. BTW, both the SQL Anywhere Monitor and Foxhound specify -sb 0 as well as -xd. |
|
[placeholder answer] |
I didn't know about -xd until I looked at the SQL Anywhere Monitor command line... am I guilty of reverse engineering? <g>
Thanks Breck for pointing out the error in the docs. I have asked the doc team to correct the error. I completely agree with you that -xd is highly recommended when deploying an application, so I've also asked the doc team to state this in the docs.