Hi!
We have a Microsoft SQL Server 2000 SP3 running database for Microsoft
Navision 3.7
From time we encounter problems, especially when running heavy query
procedures from Navision, with the transaction log. It's actually setup as
folows:
File properties:
Allocated space - 10 gb
File growth By size (100 MB)
Restrict file growth (MB) 20000
OPTIONS:
Recovery model: simple
Settings: Autoupdate statistics, Auto create statistics
We get the following errors (once every 2-3 months so far):
The log file for database 'ME_Prod' is full. Back up the transaction log for
the database to free up some log space..
How do I have to setup my transaction log file in such manner, that it won't give me the same error?
What is the good/besdt practice to go around this problem?
We have a Microsoft SQL Server 2000 SP3 running database for Microsoft
Navision 3.7
From time we encounter problems, especially when running heavy query
procedures from Navision, with the transaction log. It's actually setup as
folows:
File properties:
Allocated space - 10 gb
File growth By size (100 MB)
Restrict file growth (MB) 20000
OPTIONS:
Recovery model: simple
Settings: Autoupdate statistics, Auto create statistics
We get the following errors (once every 2-3 months so far):
The log file for database 'ME_Prod' is full. Back up the transaction log for
the database to free up some log space..
How do I have to setup my transaction log file in such manner, that it won't give me the same error?
What is the good/besdt practice to go around this problem?