|
|||||||
| Home | Register | FAQ | VB Image Host | Members List | ![]() |
Want VIP?? | Arcade | Search | Today's Posts | Mark Forums Read |
|
Welcome to the Piяator Community forums. You are currently viewing our boards as a guest which gives you limited access to view most discussions and access our other features. By joining our free community you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is fast, simple and absolutely free so please, join our community today! If you have any problems with the registration process or your account login, please contact us. |
![]() |
|
|
LinkBack | Thread Tools | Display Modes |
|
|
#1 (permalink) |
|
Private
![]() Join Date: Jun 2007
Location: Milwaukee, WI, USA
Posts: 768
Thanks: 5
Thanked 12 Times in 12 Posts
|
SQL Transaction logs filling fast
Hello. I need to know if anyone has experience with MSSQL. The problem I am having @ work is that some of our clients have databases in which they have 100mb for data and 200mb for transaction logs. We run into the issue where their transaction logs fill up fast and then of course their site errors. What is the most effective way to prevent this from happening.
I am looking for a specific query that can be done locally on the server through enterprise manager. I would also like suggestion on maintenance plan for this if anyone has ideas as well. |
|
|
|
|
|
|
|
![]() |
| Thread Tools | |
| Display Modes | |
|
|
| FirePremiums |