Before you begin backing up a SQL Server database, you need to know which recovery model the database is using. There are three different recovery models: FULL, BULK_LOGGED, and SIMPLE.

One configures SQL Server for high availability (HA) in anticipation of some event that will cause a critical application to go offline unexpectedly-a software glitch that causes an app to freeze or a ...

While the press concentrates on IP-based storage-area networks, it seems that every conversation with vendors or end users about IP storage eventually turns to a discussion of IP-based data ...

You see, we cannot use the transaction log for recovery with the Simple recovery model. Again, the document continues: “If you need to remove the log backup chain from a database, switch to the ...

CNT appliance provides SAN-based heterogeneous data-replication services over unlimited distances. Written by Rick Broida, Contributor Oct. 27, 2004 at 6:52 a.m. PT ...

Hyperscale, at present, has a few limitations compared to other SQL Server technologies. For example, it does not have a feature for long-term retention backup, simple recovery model or bulk logged ...

I think your problem is that the recovery model for your database is probably set to full, which you probably should have it set to Simple then it wouldn't use up as much log space.