Just thought I'd post an update on this in case someone else runs into this.

Our problem turned out to be related to server hardening (for security). One of the...

Easy:

ALTER DATABASE Mydatabase SET RECOVERY FULL

ALTER DATABASE Mydatabase SET RECOVERY SIMPLE

ALTER DATABASE Mydatabase SET RECOVERY BULK_LOGGED

Just a point to note - even though this is a vendor product, you can still create additional indexes if you identify a need for them.

HOWEVER, the vendor may then...

Unfortunately, we're stuck with SP3 for the moment due to other requirements.

In isolation, we know what the 8152 means - we just have no idea why it has happened when...

Are all the databases set to FULL recovery? If there are any in SIMPLE recovery model then the log backup will fail.

I'd agree with the other posters - you can do it, but you should be a little cautious.

I'd have no issue doing this on a development server where performance is...

sp_spaceused gives you this sort of info:

database_name database_size unallocated space

--------------------------...

That looks like the one I had! I think it works a bit better than the links I posted. Wish I knew where I originally found it though...

The registration entries are all kept in the Windows Registry.

I have a .vbs script somewhere that does this using DMO, but I can't remember where I found it. The good...

It depends on how up-to-date you want the database on the backup server, and how much data loss you can afford.

If you want it as current as possible, you're looking...

Put ECHO ON at the start of the .cmd file, and redirect the output to a file and see what is happening.

Could be a DOS environment issue or path issue.

Usually leave them on a Dev system, but always removed from Production systems.

Well, for one of our clients, certain development teams have a process that we call "Testing in Production"...

If you enforce DRI through the DBMS, you know it will be enforced for any relevant DML operation, no matter whether it is done via the application, or from an...

Check the directory that it is supposed to be in, and then use the Startup Options -e flag to start sqlservr.exe

Sounds like you have a bad entry in your registry.

-eerror_log_...