|
|
Posted by DataPro on 10/02/76 11:48
Many thanks for the thoughts. Being brand new to SQL Server (coming
over from DB2) have much to read and learn.
Here is my situation. An application upgrade occurred over the weekend
which made several database changes. Now the active log is at 12 Gigs.
Taking a full database backup and a log backup is not truncating the
log. Issuing a backup log truncate only has no effect.
I ussed a dbcc loginfo against the database and it returned 308 rows. I
am assuming that these 'virtual logs' represent active non-committed
transactions.
Is that right?
We are talking to the application vendor asking him why this occured.
In the meantime,,,,
Any thoughts on how I can reduce the size of this log? From what I've
read about shrinkfile it doesn't appear to be relevant here.
Any thoughts or suggestions would be appreciated.
Navigation:
[Reply to this message]
|