Yep that works and for info I have used in anger in a merge replication setup when SQL Server got the next seed value corrupt.  It somehow had its next...

Agree with Mathew, slight variation would be to use a DTS package then schedule it as a job under SQL agent and either you or if end user has access just...

If you have done a std sql2005 install (at least the client tools, doco etc no need for the database engine) then you'll find it under    

start , all programs, microsoft...

Sounds like backups you are doing are fine and if you are able to take full db every 4hrs sounds like small databases and lots of disk is available.  I...

Once the log has grown, checkpointing won't shrink it physically, the inactive portion still occupies space at the filesystem level.  Use dbcc shrinkfile. 

I would issue a 'backup log with...

As this problem started after reboot, and the frequency is so specific, I would check that the SQL agent service account was not altered or that the account it uses...

First some questions.

1.  What version of SQL Server?

2.  What error message(s) are you getting?

3. Are you connecting to a default or named instance of SQL Server?

4 What does the connect...

Thanks for the idea Miguel, not sure what impact this has on the data though??  I have a lot of databases that I have migrated to the 2000 environment, I...

Via Query Analyser 

backup log insertdbnamehere with truncate_only

Then shrink the tlog file either using dbcc shrinkfile or via Enterprise Manager

all tasks

shrink database

selecting the log file

This should reduce physical size...

Not sure exactly what the last two posts refer to as the initial question does not imply that they want to apply tlog backups between diff backups. The method of applying...

I encountered same error installing 2005 express edition on a laptop.  Same install package worked fine on a server but got the error on the laptop so my guess is...

I tend to agree with Rudy, not tested but I also would think that as each instance has its own process and memory footprint.  Each would I think be limited...

Well guess what, I was wrong (thats a first

No idea where I got that idea but MS does indicate that ent edition of RS...

Sorry your problem is not clearly explained, but as a start you should be installing the same Edition of RS as SQL server.

i.e std edition sql server means std edition of RS.

No the previous post was referring to disk space not memory.  Before you backup the source database do the following:

backup log 'dbname' with truncate_only

then shrink both the db and log...