This blog post is written in response to T-SQL Tuesday hosted by SQL Server Insane Asylum.
The idea of this post really caught my attention. Automation – something getting itself done after the initial programming, is my understanding of the subject. The very next thought was – is it good or evil? The reality is there is no right answer. However, what if we quickly note a few things, then I would like to request your help to complete this post.
We will start with the positive parts in SQL Server where automation happens.
If I start thinking of SQL Server and Automation the very first thing that comes to my mind is SQL Agent, which runs various jobs. Once I configure any task or job, it runs fine (till something goes wrong!). Well, automation has its own advantages. We all have used SQL Agent for so many things – backup, various validation jobs, maintenance jobs and numerous other things.
What other kinds of automation tasks do you run in your database server?
This part is very interesting, because it can get really ugly(!). During my career I have found so many bad automation agent jobs.
Automation is necessary but common sense is a must when creating automation.
Reference: Pinal Dave (http://blog.SQLAuthority.com)