Skip to main content

TSQL2SDAY #12 - Why are DBA Skills Necessary?

WOW this is the 12th TSQL2Sday albeit this month’s is week early because of the PASS summit next week, so these little blog parties have been running for a year now. This month is being hosted by none other than Paul Randal (Blog|Twitter) and we are going to be discussing Why are DBA Skills necessary?
There is a wide range of topics that I could write about here and Paul has listed several topics areas on his blog, I am going to be discussing how business continuity could be affected by a lack of DBA skills.
Paul in his Master class, in London in the summer just gone (review here) gave a great example from his time with Microsoft when a bank got their disaster recovery plan wrong and it ended up costing them dearly, I’m won’t go into much more than that here but it was a great story demonstrating firstly how important data can be to company or firm and also how important it is protect and look after that data – ultimately in lots of cases (backing up the database) = (backing up the business). Business Continuity and Disaster Recovery are one the main responsibilities of the DBA and it is important to get it right, not only for the safety of your own job but also for the safety of the business.
Thankfully, (knock on wood) I count on one hand the times I have needed to restore a production because of a disaster or an unexpected  problem of some kind, fortunately when those situations have come about I have been fully prepared and practiced for it and had relevant up to date documentation on hand that made the process as painless as possible. Database backups are only good if you can restore and recover from them, so I would recommend that anyone with responsibility for backing up a production database has a process in place for periodically testing those backups so you can have confidence in your restore process should the need ever arrive.
If you are backing up your databases regularly, hopefully you are also storing your backups in a secondary location(s) hopefully on a different server, hopefully off site some place so if your main building becomes unavailable…for whatever reason you can get your database back online by using the backups stored in a separate location.
I see lots of forum posts, “my database is corrupt and I have no backup please help”, “my database has accidentally been deleted, can I get it back without a backup?” which means lots of businesses out there is the big wide world are suffering because they didn’t have the essential skills of a DBA. All of these could have been prevented if someone with DBA skills/knowledge had been involved with DR Business continuity plan

Comments

Popular posts from this blog

SQL Server 2012 and Virtual Service Accounts

This post is written by David Postlethwaite
If you are using SQL Server 2012 you will probably have noticed that the default account for the SQL services has changed from that used in previous versions. With SQL 2005 and 2008 the default account for SQL service and SQL Agent service was “NT Authority\System”. This is one the built in accounts on a Windows machine, managed by the machine and selectable from a dedicated dropdown list

The Network Service account was introduced in Windows 2003 as an alternative to using the LocalSystem account, which has full local system privileges on the local machine, a major security concern.
The Network Service has limited local privileges easing these security concerns but when many services on a machine use the Network Service account it becomes harder to track which service is actually accessing resources and performing actions, because all the services are using the one Network Service account.
Also, this account, by default, has sysadmin per…

Always Encrypted

By David Postlethwaite

Always Encrypted is new features in SQL Server 2016 and it is also available in Azure SQL Database. Here you can encrypt columns in a table with a master key and a certificate so that they will appear as encrypted strings to those who don’t have the required certificate installed on their pc.
Once the certificate is installed on the computer then the unencrypted data can then be seen as normal.

The data passes from database to your application as the encrypted value, only the application with the correct certificate can unencrypt the data so it is secure across the wire. This will go some way to resolving the concern of people worried about putting their sensitive data on a shared server in the cloud such as Microsoft Azure and accessing the data across the Internet.

At the time of writing Always Encrypted is only supported with ADO.NET 4.6, JDBC 6.0 and ODBC 13.1 but expect other driver to become available.

The calling application (including SSMS) must also hav…

New in SQL Server 2017: Graph Databases

David has recorded and published a video of his presentation on SQL Server Graph Database. In his video which you can watch below, David provides an excellent introduction into SQL Server 2017 Graph Databases. In his presentation he looks at Tennis results at tournaments for  his favourite player "The Fed"  Rodger Federer.

David  shows how to set up graph database and work with them in SQL Server 2017.

Graph Database is not new. Other vendors have had graph database capabilities for some time so Microsoft are quite late to the market. In David presentation it appears that Microsoft have done a reasonable job of implementing some of the graph database features but he does point some of the limitations of the Microsoft product too and suggests that it is not ready for production yet but Microsoft seem serious about this feature.

Please watch the video and feel free to leave a comment or feedback - David is delivering a version of this talk on Graph databases in SQL Saturday Ka…