Setting Up for Success

A good dba is ready for problems. A key part of being ready is making information available and no joke I like code which broadcasts what is going on. Using raiserror with nowait and 0 or 10 severity is great. Using a stored procedure template which logs parameters, run times, errors and any other juicy information collected during the execution to a table is great. Job output files are great. Emails and texts from sql server are great. Event notifications are great. Job completion messages are great. Yippee!!!

Something I’ve never yet used are continuously running traces. I’ve set up C2 auditing and of course used traces for detecting a specific login, performance tuning and troubleshooting work. I understand this technique is popular with dba services. I wonder when the time will come for it being needed where I work and how I will recognize the situation?

This entry was posted in DBA. Bookmark the permalink.

2 Responses to Setting Up for Success

  1. Marlon says:

    Thanks for enabling me to get new ideas about cptmuoer systems. I also have belief that certain of the best ways to maintain your laptop cptmuoer in excellent condition has been a hard plastic-type case, as well as shell, that suits over the top of your cptmuoer. Most of these protective gear are usually model precise since they are made to fit perfectly across the natural covering. You can buy these directly from the owner, or via third party sources if they are for your notebook cptmuoer, however don’t assume all laptop could have a covering on the market. All over again, thanks for your ideas.

Leave a Reply

Your email address will not be published. Required fields are marked *