Viewing 9 posts - 1 through 9 (of 9 total)
Thanks again for the help.
May 31, 2013 at 2:04 pm
My script is below.
backup log mydatabase
to disk = '\\someserver\backups\logbackup_timestamp.bak'
with no_truncate, init
May 31, 2013 at 1:37 pm
Thanks for the help.
May 31, 2013 at 12:58 pm
I attached the results. There are 935 rows.
May 31, 2013 at 12:51 pm
My log_reuse_wait_desc is 'LOG_BACKUP' (recovery_model_desc = FULL). Is this correct? I appreciate all the assistance.
May 31, 2013 at 12:28 pm
Thanks for the reply. The log file is not being reused after backup and there are no active transactions (DBCC OPENTRAN) causing the size. I did not have this issue...
May 31, 2013 at 9:41 am
Ther eis a trigger that does an additiional delete and insert. That would explain this. I see the same results for updates where it shows (1 row(s) affected) then the...
September 29, 2010 at 2:01 pm
That was it. Stupid mistake on my part. Thank you for the help.:satisfied:
August 8, 2008 at 11:48 am
I use the ASCII function to return the ascii characters of the string and it returns char(32) numerous times on the end of the string. When I run a REPLACE...
August 8, 2008 at 11:42 am
Viewing 9 posts - 1 through 9 (of 9 total)