Does anyone know in Sql AnyWhere, how can I set the ReadOnly property of any database to On? I can only see the way to access the property, but cannot find the way to set it correctly at the first place.
Thanks in advance.
I've recently become responsible for administering an application which is essentially a front end to a Sybase SQL Anywhere 9 database, including the database itself. I'd like to use unload table to efficiently export the data for backup and, in the case of a few tables, ETL to get it into a reporting database / small scale data warehouse.
The problem is that the client application crashes and leaves dead connections and shared locks on a pretty regular basis, which seems to prevent unload table from getting the (brief) exclusive locks it needs. Currently I use Sybase Central to verify that these connections are in fact zombies and drop them myself at the end of the day / week.
Is there a command or script to drop all connections? Being able to drop everything at once after verifying that they're unneeded would be quite helpful but I haven't found a way to do it.
Currently I have a SQL Anywhere (version 10) database (.db and .log files) - the idea is to extract the data and utilize it for a MS SQL database.
The problem is that I start a SQL Anywhere server and attach the database in question to it, but then when I try to connect to the server, I cannot pass the authentication (I've tried the default dba/sql combo and Windows integrated security).
However, I can use the same server to access the SQL Anywhere demo database without any problems. This leads me to believe that the user authentication is tied to each SQL Anywhere database and not to the SQL Anywhere server which is currently running.
I've read some of the SQL Anywhere Database Administration official documentation, but I didn't come across any strict details on how authentication is handled.
In short, the question is if one can connect to a random SQL Anywhere database which has been just provided by a 3rd party?
Best Regards,
Borislav
So this may seem like a silly question but I have been unable to find documentation that supports either side of the question.
SQL Anywhere 10 - dbsrv10.exe has numerous startup options. I'm being told by some near me that the service can not combine cache specific command line options.
A specific example would be:
dbsrv10.exe -c 50M would set the initial cache size to 50 MB
dbsrv10.exe -ch 500M would set the max cache size to 500MB
It would make sense to me that I would want and be able to control both the initial and max cache values and use the startup string that combined both switches.
dbsrv10.exe -c 50M -ch 500M and get both an initial value and a max value configured with the startup of this db instance.
I'm working on getting some confirmation from Sybase themselves but while I wait I figured I would throw it out to anyone on here that might be using SQLAnywhere.
Can I combine the -c and -ch startup options when launching dbsrv10.exe? Is anyone doing this?
We are currently experiencing a growing temporary file problem. Watching one of our sites we can see a growth of 100 - 200 MB a day at one site we are watching. At this site a failure occured when the temp file reached 20Gb and a free space issue occured.
We are currently suppressing timeouts. -ti and -tl are set to zero. What is the chance that temp tables are building up due to this configuration?
Additionally. To further my understanding of the -tl flag, is the following a true statement: The connection will not be reset unless the client can not be reached via tcpip.