jacksonandrew321 (10/29/2014)
improper shutdown of the sql server services,
Not unless the files are damaged in the process. SQL is perfectly capable of recovering from unexpected shutdowns
not enough disk space when writing to the database,
No, that just results in the transaction trying to write failing and rolling back.
sql server can’t access log file data while in online mode (because of antivirus programs),
Only time an antivirus could do that is before SQL opens the database (before it gets a lock on the file). If that happens, the database goes RECOVERY_PENDING, not SUSPECT. If the log file disappears while SQL is running (drive failure), the DB goes into a read-only state, not suspect.
sql server goes down to shutdown in the middle of transaction which results in log file corruption etc.
Well that won't cause log file corruption, SQL is perfectly capable of shutting down in the middle of transactions and recovering safely
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability