February 15, 2013 at 11:03 am
tony28 (2/15/2013)
it was just on test DB, if i did this test http://sqlblogcasts.com/blogs/tonyrogerson/archive/2006/11/10/1280.aspx and after appeared error with FULLBACKUP LOG and when I wrote command dbcc shrinkdatabase ('Your-Data-Base-Name', TRUNCATEONLY) it showed error like this topic
Why are your shrinking your database? It's not going to fix a full log error, will make it worse if anything.
after I found this site, where I first tried very inelegant way, how someone writes and it worked, then i could do this test and it worked.
Gah, that is horrid advice on that so-called accepted answer, absolutely horrid.
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
February 15, 2013 at 11:25 am
June 10, 2013 at 5:58 am
...or it could be as simple as not properly committing /rolling back an open transaction. It was for me. Catch all error messages can have us fixing all kinds of things that aren't broken.
August 12, 2013 at 3:43 am
This error can occur after you add a column to a table.
If you retrieve that table all columns using * in the view definition it can happen whenever you trigger an intead of trigger on that view.
To fix it you have to update (alter) the view.
Viewing 4 posts - 31 through 33 (of 33 total)
You must be logged in to reply to this topic. Login to reply