I have been asked to identify some best practice "post implementation" (i.e. DB servers in production) routine security maintenance and monitoring tasks that a good DBA should be performing on routine basis specific to MSSQL. I was thinking along the lines of ensuring latest patches applied, occasional vetting DB level accounts and permissions once per quarter, ensuring no config changes have been made outsid change cotnrol etc. Can you give some pointers on any self audits you do to routinely reverify the security configuration of your Databases, and how often you do such checks.
Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline
If you have heard of RFC822 date formats, they can be quite a challenge in SQL Server. RFC822 is an Internet standard format for email message headers, including all dates within those headers. The RFC822 protocols are available in detail at:
The Delta outage: 650 cancelled flights, more than 1200 delayed flights, thousands of frustrated customers, tens of millions of dollars in damages – plus untold reputational damage to one of the world’s most trusted airlines. All due to a catastroph…