I have seen a lot of Shared hosting companies restricting the growth of MDF and LDF files of sql databases. I have not yet figured out how do they restrict the size of the LDF files as I know they are the transaction log files and once full, they will not allow any query to be executed or sql transactions to take place. What surprises me more is that they restrict it to up to 50 MB or 100 MB which I believe is very less. What is the workaround provided by them in case, the LDF file of a particular database is full? I am sure they might not be manually clearing the ldf file as it is a costly overhead. Also shrink does not always work since many a times, there is no free space available in the log file. Any idea what is the approach of the hosting companies in this matter. I am myself looking at restricting the database size, but before that need to clear my doubts.

Is this regarding MS-SQL Servers? Sorry about my ignorance.
I've passed this onto our Windows server team but the bulk of our customers are on Linux & MySQL and we monitor servers daily and hardly see any sql errors or restrictions.

We also use monitors to keep an eye on resources on a account by account basis. This helps us keep servers running smooth and fresh while managing high resource websites.

Is this regarding MS-SQL Servers? Sorry about my ignorance.
I've passed this onto our Windows server team but the bulk of our customers are on Linux & MySQL and we monitor servers daily and hardly see any sql errors or restrictions.

We also use monitors to keep an eye on resources on a account by account basis. This helps us keep servers running smooth and fresh while managing high resource websites.

Do you have an automated mechanism in place which takes care of the monitoring and what is the limit you have set for the usage of any resource?

For MS SQL, we allow a total database size (MDF and LDF) of 2GB. :)

You can ask your hosting provider to try shrinking the logs from their side.

You can have automated maintenance plans which automatically truncate the log files. I don't host SQL for folks, so I'm not sure if this is how large providers do it or not...

For MS SQL, we allow a total database size (MDF and LDF) of 2GB. :)

You can ask your hosting provider to try shrinking the logs from their side.

Shrinking as I mentioned doesn't always work. How do you distribute the 2 GB space between the LDF and MDF files?

Does anybody know how to create a maintenance plan to truncate the log files?

Shrinking as I mentioned doesn't always work. How do you distribute the 2 GB space between the LDF and MDF files?

It's a "soft" limit which means that it isn't hard enforced with suspension or any other artificial restriction, it just means that we have the right to say to a client you need to reduce the size of your database or pay more money if they exceed 2GB in total.

It's a "soft" limit which means that it isn't hard enforced with suspension or any other artificial restriction, it just means that we have the right to say to a client you need to reduce the size of your database or pay more money if they exceed 2GB in total.

So, you mean you allow the database to grow beyond 2 GB and if it grows, then tell the customer to reduce the database size or pay for additional space?