The maximum length of a Varchar depends on the version of Sybase you are using. 11.9 and below was 255.
Version 12.5 and onwards has maxium length of about 32KB - much bigger :-}
Whether it's "better" to store as a text type depends on what you want to do with it. Sybase increased the maximum...
What version of Sybase ASE are you using? I had a problem that sounds similar that was due to corruption in the procedure cache (memory area that holds procedures) - it started happening when I upgrated to 2003 and version 15. Once I rebooted the ASE it cleared up - but I had to reboot a few...
Sounds like you haven't sourced the SYBASE.sh file, which contains all the Sybase environment variables.
You can check quickly with:
env | grep SYBASE
If you're not getting a load of output, source the file with something like this (depends where you've installed sybase to)
...
The standard way to monitor the transaction log is to put a "free-space threshold" on it. Basically, you tell Adaptive Server to do something when the log gets X percent full. You can get ASE to call a stored procedure that YOU write - this proc can dump the transaction log, or write to an error...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.