October 18, 2011 at 9:33 am
Did there used to be a way before SQL Server 2008 to truncate the transaction log for a database in Full recovery mode without doing a transaction log backup? A command, not something that involves changing the recovery mode? I'm trying to troubleshoot some third party software and it'd make sense if this option existed in the past, but has been removed in 2008.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
October 18, 2011 at 9:36 am
October 18, 2011 at 9:40 am
Stefan Krzywicki (10/18/2011)
Did there used to be a way before SQL Server 2008 to truncate the transaction log for a database in Full recovery mode without doing a transaction log backup? A command, not something that involves changing the recovery mode?
Yes. Backup log ... with truncate only. Deprecated in 2005, removed in 2008 (good thing)
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
October 18, 2011 at 9:52 am
Yeah, that's what I thought, but I wanted to make sure I was reading and remembering correctly, thanks! I'm pretty sure the third party software was using that method and is still trying to do so on SQL Server 2008.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
October 18, 2011 at 9:55 am
On 2008 it'll just fail quietly. There was a traceflag to make it fail on 2005 as well, don't recall offhand.
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
October 19, 2011 at 7:10 am
TRACE flag is 3031.
@stefan Krzywicki
Have a look
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
October 21, 2011 at 8:09 am
Sure enough, that's what the software was trying to do. I told them this doesn't work in SQL Server 2008 and I haven't heard back since.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
October 21, 2011 at 9:07 am
Then tell that third party software vendors to remove that option.
Muthukkumaran Kaliyamoorthy
https://www.sqlserverblogforum.com/
October 21, 2011 at 9:09 am
Stefan Krzywicki (10/21/2011)
Sure enough, that's what the software was trying to do. I told them this doesn't work in SQL Server 2008 and I haven't heard back since.
October 21, 2011 at 9:09 am
muthukkumaran Kaliyamoorthy (10/21/2011)
Then tell that third party software vendors to remove that option.
I've made them aware of it, as I said, I haven't heard back since I told them.
--------------------------------------
When you encounter a problem, if the solution isn't readily evident go back to the start and check your assumptions.
--------------------------------------
It’s unpleasantly like being drunk.
What’s so unpleasant about being drunk?
You ask a glass of water. -- Douglas Adams
Viewing 10 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply