Who Needs Change Management?

By Guest Authors on 15 June 2003 | Tags: Administration


You’ve spent thousands of dollars on that cool technology; clustering, redundant controllers, redundant disks, redundant power supplies, redundant NIC cards, multiple network drops, fancy tape backup devices and the latest and greatest tape technology. You’re all set. There’s no way your going to have downtime.

But one day something does go wrong, is it the disks, no way you’ve implemented RAID with hot swappable hard drives, is it the server, can’t be you’ve got your servers clustered and any downtime due to failover would be so small that hardly anyone would even notice it. Well if it’s not your stuff it must be the network. Those guys are always making changes and not letting you know about it until there’s a problem. No, checked with them, no changes. What’s left? It must be the application. Once again that application group rolled out a new version and no one informed the DBAs. Once again foiled, the application team says no changes went out.

Link: Who Needs Change Management?


Related Articles

Advanced SQL Server 2008 Extended Events with Examples (25 May 2009)

Introduction to SQL Server 2008 Extended Events (19 May 2009)

Monitoring SQL Server Agent with Powershell (24 March 2009)

SQL Server Version (29 January 2009)

Scheduling Jobs in SQL Server Express - Part 2 (1 December 2008)

Alerts for when Login Failures Strike (14 July 2008)

Using xp_ReadErrorLog in SQL Server 2005 (12 May 2008)

Moving the tempdb database (5 November 2007)

Other Recent Forum Posts

Exchange Server EDB Mailbox Recovery (10m)

Subtract total counts from previous row (62m)

Replica Node availability Node (5h)

Is there a better way to do this (padding Time field with zeros) (15h)

Frustrated SQL newbie (19h)

Impact of changing server name SQL Server (19h)

SSRS - hide rows based on the user who run the report (1d)

Incorrect syntax error and I can't tell why (3d)

- Advertisement -