Can someone help me understand this scenario? I have log shipping set up between servers A and B. I take full backups on A manually and transfer and restore them on B manually. Backup logs are taken and restored automatically according to a schedule. The schedule has a window for me take and restore a full backup.
Now, a full backup was taken in time but I failed to restore it in time before the window time ran out and log backups started shipping again. More specifically, I hadn't even started restoring the full backup before the first log backup from the new series was restored. What I'm observing is that the new log backups still appear to be restoring at the destination successfully, even though they are based on a full backup that I haven't restored yet at the destination.
Is that to be expected? Or am I misinterpreting something?
My understanding of the use of the FULL in that scenario is to physically cut down the number of log backups that need to be reapplied.
Given a particular point in time you want to reach. But our log shipping boxes we never bothered restoring a FULL unless the log shipping db died for whatever reason
Reference Reading / Similar Q&As
You might want to check out my answer that I posted in response to the question: Will VSS backups break logchain? (dba.stackexchange.com)
The explanation in my answer also links to the question How can I backup an SQL Server database using Windows Server Backup...
A full does not break the TLOG backup chain.
You can lose a full backup and still restore the database using existing TLOG backups.
You only lose the ability to restore with TLOG backups if you lose a TLOG backup file.
If you have a FULL and any amount of TLOG files, then the restore will work up until any missing TLOG file (or till the end).
> as long as you have an unbroken chain of FULL and TLOG backups you can access, you can still restore your database to any point in time, even if you have another FULL backup in-between.
^^^ I already understood that from the discussion above but that sentence summarises it perfectly. Thanks @hot2use!
But just to clarify, if I have several full backups and an uninterrupted series of TLOG backups in-between them and following the last full, I can restore the database using any of the full backups as a starting point. I will just need to apply a different number of TLOG backups afterwards, depending on which full I choose, correct?
@McNets Not sure if you were asking me or anyone in general, but just to make it clear, it's the first time in my life I'm working with log shipping. Haven't developed any preferences yet :)
I'm planning to add a read-only DB for reporting purposes and another point of DR. I'm learning (on my own), how to set up a basic AO but maybe log shipping fits better in this case.
For those wanting some context, when Life of Brian was released there was a great storm in a teacup with various folks calling it blasphemous. There was a famous televised debate staged between the Pythons and various religious bigwigs.
at the moment I'm trying to figure out how Sql Server evaluates the cardinality of range predicates that partially cover the histogram step.
On the Internet, at cardinality-estimation-for-and-for-intra-step-statistics-value I came across a similar question and Paul White gave a rather interestin...
We'll see.. good move by them anyway to hold their ground.
I question whether or not graph query languages should occur under the regular SQL umbrella or not.
It seems like not placing them as a subset of the SQL spec is a mistake for marketing reasons.
By any extent, it's safe to say that Cypher will become/is a standard of some sort. And other databases like PostgreSQL are actively looking at building graph backends for their databases.
JSON/sql for example is a totally fine spec, for querying JSON and it happened under the SQL umbrella.
It doesn't seen evident to me why a graph database would need to happen independent of SQL
Reference Reading / Similar Q&As
You might want to check out my answer that I posted in response to the question: Will VSS backups break logchain? (dba.stackexchange.com)
The explanation in my answer also links to the question How can I backup an SQL Server database using Windows Server Backup...
