jasona.work (4/3/2013)

---

So my worst-case solution to reduce the size of data in the TLogs is to do the following:

1. After-hours, switch all DBs from Full Recovery to Simple, sacrificing...

The way you mentioned in your initial post.

Not necessarily....

Abu Dina (4/3/2013)

---

GilaMonster (4/3/2013)

---

If autogrow kicks in during peak usage time, the users may well notice a degradation in performance. If you grow the file manually at a quiet time,...

One is done manually by you, one is done automatically by SQL. That's...

Rather grow the file manually, not because of file fragmentation (which may or may not be of any concern depending on the IO subsystem and a bunch or other factors)...

Check Database integrity task runs CheckDB on the selected database. Functionally, it's the same as running CheckDB on that database from a custom job (reporting aside)

The data file is the one that ran out of space, not the log, so looking at log reuse is a bit of a waste of time. Instead, you need...

Why...

DuncEduardo (4/3/2013)

---

For b) I didn't need this data and the dB is test so I put dB into Simple recovery mode and then was able to shrink the log with...

For future reference:

http://www.simple-talk.com/sql/backup-and-recovery/the-sql-server-instance-that-will-not-start/

The third party inserted it into your database and you don't have rights to run updates?

In this case, defensive programming = slow queries. If your users are happy to have...

Why do you have data with leading spaces in the tables? Why have you not cleaned that data and removed the leading spaces? (and yes, you will need an LTRIM...

So you have dirty data and would rather...

To remove spaces on the left or right of a string.

Error 5 is permission denied. The account SQL is running under does not have full control to the folder or file in question.