Transaction Log changing size
-
Why does the Transaction Log change throughtout the day. Somtimes its small other times its alot bigger. I don't understand what causes it.
-
- if you use temporary tables for your SQL or SP, if those temp tables are indexed and you have to manipulate large amouns of data
- if you use order by, group by against large tables.
- look at the index creation, check your query plans
...there are only some of them.Check your users SQL and the APP's.
-
hey, yeah i think we do. what does SP stand for?
-
Stored Procedures
-
I am interested in Bulkloading and translating without using the transaction log. it's always a truncate rebuild process, so transaction integrity is not an issue...rudimentary DW. Is there a way to stop using the log for this database? It's set to 'SIMPLE', but is there anything else I can do?
-
If you don't care about the log file, you may want to schedule a job every often to truncate the log
use <Database_Name>
go
dbcc shrinkfile (Log_Filename, 300)
go
backup log Database_Name with no_log
go
Shas3
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply