Questions[transaction-log](server)

In SQL Server 2008 R2 I have a database that has full backups nightly and transaction log backups every ten minutes. The database is in full recovery model.

The problem is that the backup files for the transaction logs are hundreds of megabytes in size but should definitely not be. There is nowhere near that activity in the database. Each backup is only for ten minutes. They are so large that after a couple days it'll completely fill up the hard disk.

Any idea what is causing that backups to be so large and how to fix?

I have a problem that is my log file in SQL Server 2008 is grown to 40Gb and I wanted to shrink it. The query I am using is

    ALTER DATABASE DatabaseName SET RECOVERY SIMPLE
use DatabaseName
GO
CHECKPOINT
GO
DBCC SHRINKFILE(transactionloglogicalfilename,TRUNCATEONLY)
GO
ALTER DATABASE DatabaseName SET RECOVERY FULL

is not shrinking the log file at more level and also the shrink log file is expanding immediately in short time only.

So where is the problem ?

I wanted to shrink the log file upto 1GB and my database size is 16GB

I have SQL Server 2008 R2

Please someone help me

I have a server running SQL Server 2005. I have nightly full backups, with transaction log backups every 15 minutes. This is a relatively small server so I am not doing any differential backups.

If one of the nightly full backups fails, is the database recoverable using the previous night's backup and all of the transaction logs for both days, or would there be a problem with the missing full backup?

I've a SQL 2005 installation and my templog.ldf file keeps growing to consume all the free space on the drive it's on. Sometimes it'll stop with a few mb free but sometimes it goes further, this being the c drive I think this behaviour may be implicated in some other issues I've been seeing.

My question is, what should I do, I can move the log to another drive but I've reason to assume it won't just do the same thing there. I'm assuming that this behaviour is likely as a result of something I can change and that 45gb is an unusual size for the tempdb log to get to. We do use a lot of temporary tables and table valued functions in our code so there is plenty of scope to use tempdb, I can understand the tempdb database growing but don't understand the reason for the growth of the templog.

So far, I've ran DBCC OPENTRAN('tempdb') to see if any old transactions are hanging around, they aren't. I've read about how to shrink the tempdb and have done this a few times, but I'm really wondering what if anything I can do to stop this happening in the first place or more details on why it might be growing so much in the first place.

==EDITS==

1) The tempdb is using simple recovery model

2) The growth in templog occurs over a couple of hours in the morning when we have some scheduled queries running, basically a load of reporting which runs out of office hours for the day ahead. The size of the file steadily grows over this time. We control how many concurrent reports are running at the same time, increasing the number of concurrent reports increases the rate at which the log grows.

MySQL has quite a few logs:

• InnoDB transaction log
• Binary log
• General query log
• Error log
• Slow query log

I know about Postgresql's WAL, which is equivalent to InnoDB's transaction log (correct?).

What about the other MySQL logs such as bin log - are there Postgresql equivalence of them?