I'm literally in tears right now because I can't find any way to turn up the verbosity of SQL Server 2005 logging. Does anyone know how to do this, because I'm about to shoot a hostage every hour on the hour.



  • 1
    There are parameters that can be used for replication jobs. What additional information are you trying to capture? – jl. Feb 14 '11 at 15:52
  • Hi jl, I'm trying to capture why my damn Confluence is failing when transferring large files from filesystem to database. Don't ask, don't tell :) – FLX Feb 14 '11 at 16:09

Generally speaking, when troubleshooting issues with SQL Server the best thing to do is to carefully watch the server using SQL Profiler traces or, in recent versions, perhaps Extended Events. These methods can catch errors that may be happening that are not percolated up through the UI and shown to a user, or may provide more detail than what is shown to a user.

The sort of verbosity that can be added to the SQL Server text logs is usually specific to very specific things and not a general problem like "failed inserts".

That being said, common causes of insertion failure are query timeout due to blocking and "out of space" in the transaction log or data files.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.