Check this link out

http://www.techurbia.com/2009/03/cannot-set-a-credential-for-principal-sa-sql-server-20052008.html

just make sure you write the trace file to a drive that does not have data files or log files on it. I typically use the backup drive. Then do...

no

you can write to a file and import to a table easily. You can write a import script for it and have everything scheduled in jobs. Job 1 start trace,...

Is this locally attached disk? Partitioning of the data on seperate file group in seperate data files would do almost nothing for performance even if it is on seperate luns...

just to make sure I would run sp_change_users_login with AUTO_FIX for every login involved.

I would also run sp_changedbowner against every database involved and set SA as the owner. If it...

you can right click in BIDS in the report template to get to parameters properties and allow it in the parameter.

The script just has to be written with a default...

transactions can be held for many reasons. My guess is when you run the checkpoint the transaction causing the issue has since completed. Is this database replicated?

Is it you do...

each parameter can allow blank values but can your script or sproc handle the blank values - you would need to set that up too

Does the database have SA as the owner?

is recovery interval set to 0? What sql 200 version are you running? Is there any active transactions running when you do not see the checkpoint occur?

you could stage the data in the one table but then break it out from there for performance. It really depends on how you are using the data too. Perhaps...

agreed. the only way you will get better performance from your setup is to increase hardware. If I had to say buy what Memory or CPU I guess I would...

you can use the NOLOCK hint on select statements or SET the isolation level to read uncommitted

for sql server 2005 and windows server 2003 you do not have enough memory or processors.

Also when you do a SELECT COUNT(*) you are scanning the whole table so...

hope you figured this out by now but the error typically occurs when you have @on_failure_Action set to 4 and @on_Failure_step set 0. It needs to be an actual step...