Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
DB Engine
SQL ServerMSDESQL Server CE
Services
Analysis (Data Mining)Analysis (OLAP)DTSIntegration ServicesNotification ServicesReporting Services
Programming
CLRConnectivitySQLXML
Other Technologies
ClusteringEnglish QueryFull-Text SearchReplicationService Broker
General
Data WarehousingPerformanceSecuritySetupSQL Server ToolsOther SQL Server Topics
DirectoryUser Groups
Related Topics
MS AccessOther DB ProductsMS Server Products.NET DevelopmentVB DevelopmentJava DevelopmentMore Topics ...

SQL Server Forum / General / Security / December 2005

Tip: Looking for answers? Try searching our database.

Optimization Blows up T-Log

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
David J. Cartwright - 19 Dec 2005 16:25 GMT
Is it normal for an opti job to blow the T-log on a 80GB db to 50 GB from
2GB?
David J. Cartwright - 19 Dec 2005 16:31 GMT
sorry wrong group

> Is it normal for an opti job to blow the T-log on a 80GB db to 50 GB from
> 2GB?
Andy Davis - 21 Dec 2005 04:47 GMT
Hi,
it *depends* , what is your Recovery Model ?! is your application write
intensive !? are you doing any Bulk Logged ?! are you doing Index Tunning /
defregmentation as Maintanance Plan !?
To Reduce size of T-Log take a regular T-Log backup , say every 30 mins .

Regards
Signature

Andy Davis
Activecrypt Team
--------------------------------------------
SQL  Server Encryption Software
http://www.activecrypt.com

 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.