Bonus. Answer to deleted question:
While MS is an ancient Sybase codeline, with many years of MS and Windoze type changes, they are no longer the same. Many commands are different, and the options are very different.
1 To determine the space left in syslogs:
SELECT LCT_ADMIN("logsegment_free
2 Do not:dump tran db_name with truncate_only
That is for development databases only, and eliminates recoverability (you will need to load db from a full db dump). For test and production databases (where Sybase-provided full recoverability is required, and they will draw and quarter anyone who interfered with it) use something like:dump tran db_name to "c:\sybase\tran_dump\db_na
Sybase has many features not found in MS, it would help if you read up on it, because it will result in less work for you. We have thresholds that can be set up to dump tran long before it gets full. Read the System Admin Guide, both volumes, it provides a nice list of routine DBA tasks; and how to accomplish them.
by: IncisiveOnePosted on 2009-07-03 at 02:14:28ID: 24771066
It is just as easy in Sybase. Depends on the version slightly, so watch for that. For Sybase ASE, under the sybase user, look for a directory tree:
They could have put it elsewhere, it is not a fixed location; if it isn't there, you need to look around the directory tree.
For Windoze, substitute % for $, change the slashes to backslashes, and of course look in C:.
If it was installed and set up correctly, the Sybase errorlog also appears in the System or NT Event Log, but that is seldom done properly.