Time to Change

, 2015-08-19

The_Brady_Bunch_Christopher_Knight_1973I recently spent two days consulting with a company on their database development and deployment processes. They are a small, capable, team of developers, database developers and a DBA who have embraced the idea that they need to be able to automate their deployments. I wasn’t in there to teach them much of anything, but to help walk them through what the possibilities were for their deployments. It was a great experience and I learned a lot. They recognized that it was time to change what they did and how they did it in order to achieve greater efficiencies. They recognized that, while they were successfully building and deploying their databases (a capable team, remember), they were experiencing pain that they could alleviate. Like Peter, it was a time for change.

I think, like Peter, people get freaked out by the idea of changing. The concept of “if it ain’t broke, don’t fix it” is not a crazy or dangerous one to have. Unfortunately though, processes can be both functional and broken if they’re just functional enough. Think about how long it takes you to prepare for a database deployment. Think about how well tested your deployments are before you get to production. Think about the number of mistakes you’ve introduced to your production environment. Think about the changes that you haven’t done because getting them into production would be too hard or take too much time. These are all indications of pain. If you’re hitting lots of pain, well Peter, it’s time to change.

The good news is, like Peter, there’s lots of support out there for you. For example, coming up in London, Friday the 16th, Redgate is hosting SQL in the City. It’s a fantastic event (and yeah, I’m saying that even though I work for Redgate). We’re going to be showing off our tools, especially some of the tools that can help you get your database lifecycle management processes under control. Want to get started on that change so that you can reduce the pain in your deployments? Then click here to register.

Can’t make it to London? How about Seattle? We’re taking the show on the road. We’ll be there on the 26th of October. Click here to sign up.

It’s time to change.

The post Time to Change appeared first on Home Of The Scary DBA.

Rate

Share

Share

Rate

Related content

Database Mirroring FAQ: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup?

Question: Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? This question was sent to me via email. My reply follows. Can a 2008 SQL instance be used as the witness for a 2005 database mirroring setup? Databases to be mirrored are currently running on 2005 SQL instances but will be upgraded to 2008 SQL in the near future.

2009-02-23

1,567 reads

Networking - Part 4

You may want to read Part 1 , Part 2 , and Part 3 before continuing. This time around I'd like to talk about social networking. We'll start with social networking. Facebook, MySpace, and Twitter are all good examples of using technology to let...

2009-02-17

1,530 reads

Speaking at Community Events - More Thoughts

Last week I posted Speaking at Community Events - Time to Raise the Bar?, a first cut at talking about to what degree we should require experience for speakers at events like SQLSaturday as well as when it might be appropriate to add additional focus/limitations on the presentations that are accepted. I've got a few more thoughts on the topic this week, and I look forward to your comments.

2009-02-13

360 reads