Either we're allowed to assume that ALL steps succeed or that Any step could fail....

therefore If all steps succeeded then the answer is YES (because you must have taken a...

Some people are suggesting that we are assuming that the log backup is successfull but that this is not explicitly stated.....

ok - to take that point further - it is...

I agree with michael kipp

I've been to quite a few events and regardless of whether the speaker is good or bad i always pick up something from the speaker about how to portray yourself...

I'd suggest scheduling a job every hour to dunp table sizes into a table and then monitor table growth (you could use excel to produce some graphs)

here's the code i...

other than that you also have

msdb..sp_help_job

(and also sp_help_job_schedule 'myjobname')

would it not be simpler to just move your distributor to another server and have the distributor runing all of the log reader and distribution agents?

in addition to all the existing valid comments : -

you should note that table sizes will be misreported by sp_spaceused if there is no clusted index on the...

are all the jobs running concurrently ? if so there is a hard limit on the number of threads that can be allocated to these jobs

details can be found at...

just out of interest - you upgraded from 2gb of ram to 8gb - did you set /3GB and /PAE in your boot.ini. if so did you do sp_configure...

Always always always remember to make your backups on a seperate array to your data files (.mdf/.ndf)

if you lose your log file (.ldf) you can recover, but to get back...

I'm with primary keys....

but i'll settle for indexes indexes and more indexes... - developers often assume that what they've written against their dev database which has 50 rows of data...

you'll need to dig yourself out of this using scripting rather than GUI tools.

as an emergency to get the log size down you might want to look at running...

LAST backup time

SELECT d.NAME,MAX(b.backup_finish_date) FROM

MASTER.dbo.sysdatabases d LEFT OUTER join

msdb.dbo.backupset b ON d.NAME=database_name AND b.server_name=@@servername

WHERE backup_finish_date>'01 oct 2008' AND TYPE='D'

GROUP BY d.name

For reference I'll post some of the procs I created previously - as and when i get time - i'd welcome suggestions from others.....

here is one to check...