Question Inherited a database server to maintain and found that the transaction log is 92 GB. My plan is to do the backup of that and get it brought back down to a regular size, then fix it. The problem is I don't have enough disk space on the machine to do …
Question This is a hypothetical question, that flows from the answer by sepupic where they explain that 2TB is the physical limit for SQL log file.
if you need it more than 2Tb you add the second log file.
I have long held the belief that multiple log files …
Question This is in relation to a rollback scenario from a 2012 -> 2016 upgrade.
The scenario is that the SQL Server 2012 database is restored onto 2016 and log files applied until it is up to date. Then production systems are cut over to 2016. Database is …
Over on Stack Exchange, someone asked why their transaction log was growing very fast during a full backup. An interesting tidbit to this question is that the database is in SIMPLE recovery – so the log should stay tiny, right?
Wrong. While taking a full …
Question This question was attempted twice on experts-exchange with no real answer.
I know that I should not shrink the log file - that is not the question.
If you feel like answering that one should not do it- that has been confirmed many times yes and it is …
Question One of our SQL Server 2014 database transaction logs is growing very fast and I cannot find the root cause for this.
Database in Simple recovery mode. During full backup the log file grows to its limits (800GB) and backup fails.
Have you ever wondered what the best option is for making your data available in your environment? I was asked by Carlos L Chacon (blog|twitter) to be part of a panel on his podcast for an episode discussing some of the options–availability groups, mirroring, …
Question Imagine we have two nodes participating in SQL 2012 AO. This is a test instance. During one of the index rebuild operation the log was grown up really big (250 GB). We are unable to back it up due to space constraint. What if we backup the Tlog to …