title: Is it normal to lose 30 minutes of data on a SQL Server crash?
body: <p>We have worked with Oracle for a number of years and we now need to develop a new application using SQL Server in AWS for the first time.</p>
  <p>What surprised us, is that the new SQL Server DBA told us off the bat that SQL Server uses some kind of replication every 30 minutes (or with 30 minutes delay, I don't remember): in short, he said that on an AWS SQL Server crash, when the secondary server comes up &quot;we will lose <em>only</em> 30 minutes of data in Production&quot;.</p>
  <p><strong>EDIT</strong>: By &quot;crash&quot;, we mean the primary server is dead/unrecoverable.</p>
  <p>We never expected this as a normal behavior and we haven't seen something like this in Oracle... ever.</p>
  <p>Is it normal to expect to lose 30 minutes of <strong>commits</strong> on a SQL Server crash? This would include payments, invoices, and other transactions that we would consider quite important.</p>
  <p>Should I push back about this, or this is considered normal in SQL Server?</p>