transaction log sensativity

[mike718]

I am new to DB Administration. I have a database that I Dump and restore to another server nightly (7PM). I have hourly transactions that are backed up and restored hourly from 7am - 6pm. My 7am transaction log is always considerably larger that the others throughout the day. I a 500KB transaction per hour. The first transaction in the morning is 1,260,000KB. I have a feeling that the full DB dump is somehow being logged. Can anyone tell me how I can turn down the sensativity of the transactions?? Also my .ldf file continues to grow throughout the day even though my transactions are scheduled hourly.

Thanks

Mike

 

[JayKusch]

Please define what you mean by "Dumped". Is this accomplished w/ a backup or are you exporting the data using DTS or is it simply INSERT INTO statements that you are running.

Thanks

J. Kusch

 

[SQLBill]

What else are you doing on the database? Are you running any maintenance programs, such as DBCC INDEXDEFRAG?

Some maintenance programs cause transactions to occur.

-SQLBill

 

[mike718]

What I mean by dumped is a backup. I do a full backup dump nightly and a transactional backup hourly.

I am not running any maintenance programs.

 

[JayKusch]

Well, you backup and tlog backups are not the culprit to the large TLog.

Thanks

J. Kusch

 

[SQLSister]

Why don't you set up profiler to run during the night and see what actions are happening in that time period? You might be surprised to find something happening.

Alternatively you could keep running the transaction log backups every hour all night long and see if you can further refine exactly when the large number of transactions are happening. Then run a profiler trace just during that time period rather than the whole night.

Questions about posting. See faq183-874