Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Syslog Vs Transaction Log
- Thread starter Kum123
- Start date
hello,
syslogs is a system table in sybase and it contains the transaction log... this is used by ase for recovery and roll forward...
a user cannot update, delete, or insert the syslogs table...
here are the columns:
xactid - transaction id
op - number of update operation
when your transaction log fills up this is an indication that your tempdb space has ran out... syslogs will inform you to increase your tempd size or create/run sp_thresholdaction stored procedure to dump the transaction log...
you can monitor the server log files found under the install subdir in /home/sybase... depending on the directory structure standard you are using...
ciao,
q.
syslogs is a system table in sybase and it contains the transaction log... this is used by ase for recovery and roll forward...
a user cannot update, delete, or insert the syslogs table...
here are the columns:
xactid - transaction id
op - number of update operation
when your transaction log fills up this is an indication that your tempdb space has ran out... syslogs will inform you to increase your tempd size or create/run sp_thresholdaction stored procedure to dump the transaction log...
you can monitor the server log files found under the install subdir in /home/sybase... depending on the directory structure standard you are using...
ciao,
q.
Guest_imported
New member
- Jan 1, 1970
- 0
The above answer is wrong.
syslogs and transaction logs are the same thing. It is a system table - and EACH database has one. It contains all info needed to rollback a transaction.
Management
A database's transaction log will grow until it runs out of space - or you take some manual action to truncate it - or you can also make it automatically truncate (- but then loose the rollback ability)
syslogs and transaction logs are the same thing. It is a system table - and EACH database has one. It contains all info needed to rollback a transaction.
Management
A database's transaction log will grow until it runs out of space - or you take some manual action to truncate it - or you can also make it automatically truncate (- but then loose the rollback ability)
- Thread starter
- #5
Hey guys,
Lets not try to prove ourselves over each other.
Well, we are talking the same thing, except, qyllr mentioned about tempdb. Tempdb is not at all linked to syslogs. Syslogs are independent and every database has its own syslogs. Tempdb is a common place which system automatically uses for temp tables and its own working tables.(Ofcourse you can use tempdb as other db and it is being rebuilt everytime the ASE restarts.)
For my installation, I have 2GB tempdb and for one of my database I have 3GB syslogs. I have batch jobs running weeknights which pump-in/refresh data from other resources to our DW database. I am 99% sure my transaction log doesn't get filled-up completely due to the batch jobs, but still sometimes the server throws error messages saying "Syslog is full. Dump your transaction or increase the size of log".
Is there a limit on the number of logs(I mean number of rows) in the syslogs table, regardless of the size alloted?
Tx,
Lets not try to prove ourselves over each other.
Well, we are talking the same thing, except, qyllr mentioned about tempdb. Tempdb is not at all linked to syslogs. Syslogs are independent and every database has its own syslogs. Tempdb is a common place which system automatically uses for temp tables and its own working tables.(Ofcourse you can use tempdb as other db and it is being rebuilt everytime the ASE restarts.)
For my installation, I have 2GB tempdb and for one of my database I have 3GB syslogs. I have batch jobs running weeknights which pump-in/refresh data from other resources to our DW database. I am 99% sure my transaction log doesn't get filled-up completely due to the batch jobs, but still sometimes the server throws error messages saying "Syslog is full. Dump your transaction or increase the size of log".
Is there a limit on the number of logs(I mean number of rows) in the syslogs table, regardless of the size alloted?
Tx,
i would suggest the following:
1. make sure you either dump your tran log or have truncate log on checkpoint set on.
2. schedule a sp_helpdb to run on the db while your batch process is running. this will show you space available in the log and will tell you if it is filling up. my experience is that the computer is usually right. so if it stays it is, then likely it is.
I do not believe that there is any practical restriction on the log. i have run a system with 5Gb log and it used all of it. Paul
1. make sure you either dump your tran log or have truncate log on checkpoint set on.
2. schedule a sp_helpdb to run on the db while your batch process is running. this will show you space available in the log and will tell you if it is filling up. my experience is that the computer is usually right. so if it stays it is, then likely it is.
I do not believe that there is any practical restriction on the log. i have run a system with 5Gb log and it used all of it. Paul
- Status
Similar threads