You can increase performance by telling the server that it does not necessarily have to write to the log file at the same time that it commits data. This allows the server to write to the log file later, perhaps when the server is less busy, or when several transactions can be written at once. This is called “relaxed durability”. It increases performance by decreasing the I/O (Input/Output) load.

If you set the transaction durability level to “relaxed”, you risk losing some data if the server shuts down abnormally after it has committed some data but before it has written that data to the transaction log. If you use relaxed durability, some transactions may not have been written to the log file yet, even though those transactions were committed. Therefore, you should use relaxed durability ONLY when you can afford to lose a small amount of recent data.

If you want to set a maximum delay time before the server writes data, use the Logging.RelaxedMaxDelay parameter.