Skip to main content

Shrink log files in SQL Server 2008 (or later)

Some years ago, I blogged about the BACKUP LOG WITH TRUNCATE_ONLY command.  However when I tried to use the same technique a few weeks ago, it no longer worked.
When I executed the following statement
BACKUP LOG Northwind WITH TRUNCATE_ONLY

I got the following error message back.

?Msg 155, Level 15, State 1, Line 1
'TRUNCATE_ONLY' is not a recognized BACKUP option.

After some research on the Internet I discovered that ‘BACKUP LOG WITH TRUNCATE_ONLY’ is a dangerous command: it empties out the contents of your SQL Server’s transaction log without really backing it up. When you use it, you lose the ability to recover to a specific point in time.Therefore Microsoft decided to remove this capability from SQL Server 2008.

The only workaround in SQL Server 2008 is to switch the database’s recovery model to simple as shown in Books Online. Afterwards you can call the following command to shrink the logs:

DBCC SHRINKFILE(<TransactionLogName>, 1)

Afterwards you can switch back to the full recovery model.
Labels:

Popular posts from this blog

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more