Is this sql 2000? or 2005?

Use sp:completed with EventCalss, spid ,textdata , Duration, cpu, reads and writes columns only.... YOu don't need duration, cpu, reads and writes columns but you...

4.4 mil rows in 4-8 seconds is very fast ... how many total does this table contains...

Yes, it possible...

You can scheduled the job to run every 1/5/30 minutes or so...

1. Create a table with file name and path ...

2. Write a proc to check the table...

I see most of the documented dbcc writes the info to sql error log but most of un-documented dbcc not...

If you can spend money for this check for third party tools..

Post exact error details... mean time try the following...

If it is not network issue try the following...

Change the agent profile: increase your commitbatch size to 100 or 150 and try...

Both ways it can be done..

I don't think there is way other than hacking and modifying system procs...

SQL code will check the uses athentication with job ownership or sysadmin...so that you don't get the status..

You may get better info from the following...

select * from sys.foreign_keys

Another method will be add a dummy column and update... drop orignal column and add new columm...

http://www.sqlservercentral.com/columnists/pibison/alteringacolumnonareplicatedtable.asp

I don't see any problem...

1. backup database...

2. Script replication...

3. Remove all subscriptions...

4. Remove all publications...

5. Disable replication on the...or remove replication...

6. Restore all user databases on to new server.

7.Enable for...

First try to figure it out what is causing this failure...

1. Run tlog backup in a Query Analyser window and see that error do you get..

Backup log <database name> to...

can you post sp installation error you got...

Try reinstalling sp3 again...

So it was security issue.. not the sql issue...

Thanks for the correction...

http://www.microsoft.com/sql/howtobuy/default.mspx

Yes, that is correct...

Log file will not be truncated when you run the full backup...