Tag Info

New answers tagged

2

Short answer: Just leave the log file as big as it typically needs to be, and stop worrying about it. Longer answer: First, why do you want to keep shrinking the file? If it's just going to grow again (and keep in mind that shrink and grow operations are expensive, especially for the log), then what did you gain? What did you use all that freed up space ...


1

In AGs writes can only occur on the primary. Shrink operations are writes. Therefore you must do the shrink on the primary. Note that the shrink may not shrink as much as you expect, your test on the restored DB had probably leveraged simple recovery model. Read How to shrink the SQL Server log for more info. Do not shrink to 160MB. Determine why did the ...


0

Everywhere I have read on internet comes down to recycling SQL Server...surely there has to be a better way...anyone? No this is a temporary solution. I guess you posted same question before could you please tell what is total size of database you have in your SQL Server instance. Size of tempdb depends on how much your queries are using it. It cannot ...


2

Note: this post might be useful too: Issues with TempDB mdf file ever increasing Unless you can figure out what process is using that work table (and can safely kill it), I'd have to agree with what your searches have already yielded: cycle the server and you should be able to shrink tempdb. A different question has dealt with figuring this out for #temp ...



Top 50 recent answers are included