No, absolutely not.  Normal log backups in normal circumstances; a tail-log backup in extreme circumstances, for example someone has deleted a large table and I need to restore the whole...

DDL = CREATE TABALE statement, including CREATE INDEX statements.  Queries = the full query you're having a problem with.

If you're filtering on auftragdatum, that's likely to be painful,...

I think it depends on the context, not on the method.  If I'm backing up a log of a database with the intention of restoring over that database, I'd call...

When you say 58 million rows have been deleted/rebuilt, what do you mean?  What rows are affected - just those at the end of the table, or rows in random...

I'm confused about whether you're using a linked server or not.  But try something like this.  If you are indeed using a linked server, make sure you understand about linked...

Try this.  If you wanted to go to an indeterminate number of dimensions, you'd need to use dynamic SQL.  I don't know whether, or at what point, performance will become...

Like I said, this is something you need to do yourself.  It's too tiresome to expect someone else to do it for you, not to mention the fact that we...

I can't open your file - just as likely to be due to restrictions this end as to anything wrong with the file itself.  Combing through a deadlock graph isn't...

I think I must have misunderstood something.  The "Correct Answer" section lists the first three options as being the correct answers.  The Explanation section then goes on to say "All...

I think e4d4 is right.  Only use NORECOVERY in a BACKUP LOG statement if you intend to restore over the database you're backing up.  You should be able to bring...

Try this.  It involves a triangular join, so performance may not be good on large data sets.

WITH BeginningsandEndings AS (
    SELECT
       ...

SELECT
     dBookedTill AS FreeFrom
,    LEAD(dBookedFrom,1) OVER (ORDER BY dBookedFrom) AS FreeTo
FROM @t
UNION ALL
SELECT
     NULL
,    MIN(dBookedFrom)
FROM @t
ORDER BY FreeFrom