| Author |
 Topic  |
|
|
pganz
Starting Member
7 Posts |
 Posted - 01 October 2004 : 18:06:56
|
Hi,
I'm running the latest version of Snitz for a awhile now and just recently started having a problem.
I get the following error when I try to post or do anything meaningful:
Microsoft OLE DB Provider for ODBC Drivers error '80040e14'
[Microsoft][ODBC SQL Server Driver][SQL Server]The log file for database 'slopcomics' is full. Back up the transaction log for the database to free up some log space.
/forum/post_info.asp, line 981
I found in these forums that my host needs to backup the file which I asked them to do. Still having problems so asked them to do it again.
Having this problem is making me wonder if maybe I need some kind of program or front end software to work with the databases for the forums?
Is there some kind of routine maintenance that I should be doing to the databases?
Any thoughts would be very welcome.
thanks
Pete |
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 01 October 2004 : 18:25:05
|
ask your host to check what the recovery model is set to, and ask them to set it to simple if it is not.
It is your hosts job to maintain your databases that is what you pay them for  |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 01 October 2004 : 18:26:40
|
| Make sure your host is using the Simple recovery model, since it will use less transaction log space. If that happens frequently you probably need to buy extra DB space. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
pganz
Starting Member
7 Posts |
Posted - 01 October 2004 : 18:35:11
|
quote:
Originally posted by ruirib
Make sure your host is using the Simple recovery model,
Will this eliminate this problem in the future or will I have to tell my host to do a back up or something every so often?
thanks
pete |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 01 October 2004 : 20:57:01
|
| Simple Recovery will dramatically reduce the amount of SQL Log data, providing autoshrink is also enabled this should be a one time thing (autoshrink isn't strictly needed but I personally never see any harm in enabling this as well). |
Kiwihosting.Net - The Forum Hosting Specialists
|
|
|
|
pganz
Starting Member
7 Posts |
Posted - 03 October 2004 : 12:05:29
|
quote:
Originally posted by Gremlin
Simple Recovery will dramatically reduce the amount of SQL Log data, providing autoshrink is also enabled this should be a one time thing (autoshrink isn't strictly needed but I personally never see any harm in enabling this as well).
My host is still having trouble getting me back up. Maybe backing up the log file doesn't clear it?
Could they just delete the log file? Or would that cause more problems?
Thanks
pete |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 03 October 2004 : 16:45:53
|
They may need to backup the log and truncate it as well. Did they set the Autoshrink properties as well that I suggested?
BACKUP LOG {Database Name} WITH TRUNCATE_ONLY
|
Kiwihosting.Net - The Forum Hosting Specialists
|
|
|
|
pganz
Starting Member
7 Posts |
Posted - 04 October 2004 : 17:03:09
|
quote:
Originally posted by Gremlin
They may need to backup the log and truncate it as well. Did they set the Autoshrink properties as well that I suggested?
BACKUP LOG {Database Name} WITH TRUNCATE_ONLY
I'll pass this along. I don't know about the auto-shrink as I'm going thru a guy that acts as out virtual host. He is pretty good usually and in this case I think it is the guys at AIT that are slow in responding.
According to the advice I've gotten here it should be a pretty simple fix.
Thanks again and I'll post here what I find
pete |
|
|
|
Wholsea
Starting Member
21 Posts |
Posted - 31 October 2004 : 19:11:09
|
I just has this same exact issue, this is what I did to fix...
Note the extra steps before killing the log. I don't know why but the basic truncate log does not work, you have to do some of these other steps...
*Thanks Google*
drop table t1
go
dbcc shrinkfile(2,notruncate)
dbcc shrinkfile(2,truncateonly)
create table t1(char1 char(4000))
go
declare @i int
select @i = 0
while (1=1)
begin
while (@i<100)
begin
insert into t1 values ('a')
select @i = @i + 1
end
truncate table t1
backup log *databasename* with truncate_only
end
go
|
|
|
| |
Topic |
|
Topic Locked
