The topic for the golden jubilee edition is, “Automation”. What is T-SQL Tuesday? T-SQL Tuesday is a monthly blog party hosted by a different blogger each month. This blog party was started by Adam Machanic (blog|twitter). You can take part…
The topic for the golden jubilee edition is, “Automation”. What is T-SQL Tuesday? T-SQL Tuesday is a monthly blog party hosted by a different blogger each month. This blog party was started by Adam Machanic (blog|twitter). You can take part…
Automation plays a huge part in our lives and the DBA profession is no so different. A couple of years ago this topic was shared by Pat Wright. I would like to revisit this again and see how much of our approach has changed.
This whole thing, was put in a store procedure and then called from a job step for a long running job. For example, like a database backup job. And additional logic was written around the return value to write proper error numbers to application log. These event-ids where then picked up by monitoring applications and alerts where raised.
I have mixed feelings about this solution. Although, it worked without a problem (I am secretly proud that I was able to write something like this); I would have loved to just upgrade the servers to SQL 2008 and be done with it.
In this post we look at how we can REST API to interact with the SQL Azure Database Server.
This week’s T-SQL Tuesday is being hosted by Wayne Sheffield, and the topic is to blog about anything PowerShell related to SQL Server.
Today I am going to write about a few things:
-Getting a list of installed instances on a particular box.
-Reading the SQL*Server error logs using SMO.
-Querying the Windows event logs for errors.
When you are working as part of a team that manages a few hundred SQL*Server instances; sometimes, it becomes hard to keep track of all the people who need to be notified when you plan for database migrations and such. Also, if there is an issue that needs their input ($’s); we do not want to send it to the wrong person now, would we. Maintaining the information in excel sheets is good but, wouldn’t it be nice to have the information available on the DB itself? We can get all the information in one shot and send out e-mails to the concerned (correct) individuals.
Slipstream is a term used to describe merging original source media with updates and then installing the updated files. Blah..Blablablablah…Learn how to do this with Powershell 🙂