SQL Anywhere Dead Chickens

In the spirt of the "characteristic errors" listicle here is a list of "dead chickens" associated with SQL Anywhere.

If you have ANY examples of your own, PLEASE post a comment here or SEND me an email: breck dot carter at gmail dot com

---

To wave a dead chicken is to "perform a ritual in the direction of crashed software or hardware that one believes to be futile but is nevertheless necessary so that others are satisfied that an appropriate degree of effort has been expended. 'I'll wave a dead chicken over the source code, but I really think we've run into an OS bug.'" - The Jargon File

---

1. If your remote data access doesn't work, try fiddling with the declared data types; e.g., from char to varchar, or vice versa.
   

   Example: Error returning bigint from remote server
   

2. If your remote data access with Excel doesn't work, try periods, try the magic dollar sign, try NVARCHAR, try Google!
   

   Example: SELECT FROM Excel Spreadsheets
   

3. If your query takes too long, try turning off intra-query parallelism: SET TEMPORARY OPTION MAX_QUERY_TASKS = '1';
   

   Example: The New MaxBPs=768: Set MAX_QUERY_TASKS = '1'
   

4. If your WINDOW query doesn't work try adding RANGE BETWEEN UNBOUNDED PRECEDING AND UNBOUNDED FOLLOWING.
   

   Example: Reporting and the Audit Trail
   

5. If something goes wrong after installing, try rebooting.
   

   Example: Try rebooting
   

6. If ISQL READ doesn't work, try specifying the code page: READ ENCODING Cp1252 "C:\data\filename.sql";
   

   Example: Example: OUTPUT TO From VB, Part 2
   

7. If you can't connect over TCP/IP, try adding DOBROADCAST=NONE.
   

   Example: Demonstrating High Availability
   

---

If something is wrong on the internet, fix it!

---