That's normal, the file shouldn't reduce in size automatically. That suggests that log truncation is happening regularly and there's nothing wrong.

Did you read the articles?

Is the log growing or is the file constant at 300GB? If it's growing, what's the reason given?

Take a read through these

http://www.sqlservercentral.com/articles/Administration/64582/

http://www.sqlservercentral.com/articles/Transaction+Logs/72488/

I wouldn't recommend changing worker threads. 0 is a good default, it shouldn't need changing. Identifying why you're running out of worker threads should be a priority.

Maybe schedule a job...

The error message is pretty clear, you have a column in the select clause that's not included in a group by clause, as it has to be because of the...

Leave the databases that you restore in compatibility mode 100.

Doesn't mean that the server's behaving entirely as if it were a SQL 2008/2008 R2, just that some T-SQL structures and...

32 bit or 64 bit?

Have you enabled remote DAC? If not, you'll have to connect from the server...

Partitioning for what?

1000 DBs is possible (limit is 32 767), but that's...

berniesprouster (8/9/2013)

---

Further to this, I thought of suggesting one Filegroup per customer and grouping all objects for each customer into said Filegroups. This would provide for relatively easy backups/restores and...

There is nothing about simple recovery model that means it won't use the full size of the log or grow the log. Simple recovery only means that log truncation occurs...

After the restart, the DB will either be entirely available or you'll get errors in the errorlog on startup (and possibly even the DB not coming online). If the latter,...

Restart SQL or take that DB offline and bring it back online (make absolutely sure the files really are there first). Once SQL detects that a file is missing, it...

Please note: 4 year old thread.

The DAC connection requires a sysadmin, not necessarily SA, so you should be able to use that to connect.

and...