December 14, 2011 at 11:48 am
Vendor #1 creates db and supplies electronic forms for disconnected data capture by field staff. Helped me set up merge replication to push out look-up tables for those forms (and I guess allow field staff to make data changes). Collected data is not sent back through replication, but a separate process instead.
Vendor #2 supplies more electronic forms.
database gets full backup every night and trans log backups throughout the day. I always check to make sure the jobs run successfully. Our IT section handles physical server (that's my excuse), so I didn't notice the database file sizes. The database is about 100mb; but the trans log is about 30gb and growing at about 1gb every three days. "dbcc opentran" does not report any open transactions. I don't really know how to read the output from "select * from fn_dblog(null, null) ...", but there are a couple million rows.
Can someone explain (or point me in the right direction) why the trans log file is growing so big/fast?
If there are open transactions as part of replication, how can I commit or rollback those?
thanks,
Tom
December 14, 2011 at 12:11 pm
http://www.sqlservercentral.com/articles/Transaction+Log/72488/
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply