As with all debugging, the most likely thing is that the error message is telling you the truth.  The most likely cause is that one of the file paths used...

As some people have already said, you need to do transaction log backups to save your log information.  Do not use the truncate_only option unless you really want to loose...

Our standard is to use NT authentication everywhere we can.  This is mainly because NT auth gives improved security over SQL auth. 

All but 1 of our production instances only...

If you did not have a logging mechanism, you would not have a rollback mechanism.

If your logging mechanism was limited to the memory on your box, you would be limited...

You may need to think more about the impact of shrinking log files that will grow again over the next few days.

Any shrink operation will release disk space to the...

How is this any different to using SQL Server authentication?

The only reliable way to retrieve a random sample of records wit SQL Server is to use the Newid() function.  Do a search of this forum's archives for 'random' and...

There is no way to ensure you have a relationally intact set of data by taking a backup.  This is because applications can continue to update the databases while the...

SQL Mail is not the most bug-free product that Microsoft have produced.  Even though it can work for weeks without trouble, it is not unusual for mail to stop working...

If you can get a RAM disk set up, you could put the log file on there.  If you do this, you may need to  reduce the checkpoint interval so...

The Windows Event Log could give you more details of why SQL will not start. 

If this does not help, add a startup parameter of -T3608 and try again.  (Search...

There are actually 2 reasons why Full recovery mode may be necessary.

1) To allow point in time recovery using transaction log backups.

2) Provide a full audit trail of all changes...

If sa24's idea does not work, copy and paste the code in sp_changedbowner into your own user sp.  Then locate the test for system databases and remove it.  Your amended...

This is by design.  Microsoft, in their infinite wisdom, added some code to the Agent startup process to set MSDB to simple recovery mode.  If you set up the right...

According to the Microsoft documantation, the /PAE switch is not needed in W2003 - it is effectively enabled as a default.

This means all you need to do is enable AWE...