I have a couple of scripts I use weekly to monitor growth rates. Unfortunately, it's one script for 7/2000, one script for 2005. If you run the 2000...

What Tommy said, and my personal preference for growth is to used fixed size rather than percentage. Otherwise you get exponential growth. And if the database is going...

What service account is SQL Server running under? Make sure it has the necessary NTFS permissions to run the executable and write to the destination folder.

I haven't used CLR or researched it much, but as far as DML goes, surely CLR triggers would fall under the same logic as a traditional DML trigger:

1. do...

I got it right because this is exactly what I am doing hourly for one of our databases, in lieu of transaction log backups (DB is 3GB in size, generates...

Missed that. Guess I shouldn't have been looking in the KB article for a reference to the fix. 😛

Are the instances of SQL Server on each of the servers installed into the same folders? For one of them, you mentioned you installed to E:\.... What about...

It's also an annoying bug and I haven't seen a fix for it yet. I just schedule a SQL Agent job to run a vbs script (you could use...

You mentioned you changed an account. At the very least, make sure the account has an SQL login & necessary rights to the database in question (it needs to...

I'll ask the obvious - was the database being backed up? And was the backup (or a copy of it) on media (disk, tape, whatever) that was not affected...

The options are described in BOL. A brief precis:

FILE - haven't used it myself. You can have more than one backup (AKA backup set) in a single backup...

I've come across similar behaviour on our dev servers. I've had strange behaviour with integrity checks as well - the scheduled job fails but there's no indication why other...

Your network link will likely be a bottleneck. Are you going over a WAN? They can be even slower, because they are generally a leveraged/shared resource. I...

I've got 3 as well, for the reasons given above. Although I am not entirely convinced that named pipes is a protocol per se, but since it can be...

Nope. Nothing wrong with that. Like I wrote above, check for a duplicate CREATE statement - it's likely that two of them will have the same name 'Office'....