mwpreston

Collaboration is key throughout the whole process IMO

Absolutely! At the yearly least having the piece of mind that you can restore your data is important!

Thanks for the answers!

Thats great to have a group dedicated solely to db monitoring... Do you know what type of maintenance they perform? Anything out of the ordinary other than the standard re-index, defrag, etc..

Cheaper and completed faster! That's a hard thing to say no to

Thats a great point! Moving between clouds is not the most user-friendly event! I think companies like Ravello Systems are really sitting on some awesome technology that can hopefully help us with that...

You sir are in some sort of VM lifecycle Nirvana that we are all after Thanks for the comment and great work!

That's one way of putting it I guess.

Thanks! Sounds to me like you try and stay clear of all that is database

We currently use an excel spreadsheet and let me tell you it is painful - even when it is up to date!!! We are in need of something however IPAM always seems to take the back burner to other projects! If the IP isn't on the spreadsheet, we do a ping, no reponse - go for it and pray! Brutal process that has bitten us a few…

Certainly no better way to show the value of something by showing the complete solution in real time! Thx

Wow! It doesn't get much more thorough than that! You seem like a busy man!!!

OMG - Where is the DR plan we need it? "Oh, in that burning building there..."

You seem to have a very diligent baseline process - kudos to you Christopher!

Wow! You have done a great job with education your application owners if they are coming back to you with anticipations of CPU ready

Definitely aiming for future growth is a great strategy. That way you don't always have to revisit "the conversation"

For sure - a lot of times I find myself in a situation where I'm only using an application to about 10% of it's capabilities - and trying to find the time to learn more is hard

Usually an "outage" helps put the dollar amount into perspective J/K - great point - without knowing how much money will be lost, it's definitely hard to justify to C levels.

Do you include them on all support requests? I'm assuming you speak highly of Solarwinds support team.... Good to know!

Yeah, for some strange reason that is one thing that tends to be forgotten! Were they in a disaster situation when this was discovered or was it something you caught before hand?

All great points and so true - users do not care what hypervisor their applications are running on - and thus further, application owners might not care what hypervisors their cloud services are running on.... So it is a commodity in that sense, but isn't in others... A true IT consultant answer right? It depends! 

Thanks for the comment. I'm sure its nice to have a well established database team, broken down into vendor specialties at that!!!

Can't due to compliance/security policies? Or budgets?

Absolutely. Breaking things down into small achievable tasks always seems to make things easier! Thanks for the comment!

For sure! I'm a big supporter of tweaking your alerts to fit your needs. Once we start to get too many alerts from too many systems we end up filtering these messages, and not seeing the important one when it does come in!

These are all great comments with great advice. I for one find that by breaking down your org by service also helps you to discover those little scripts and tidbits that need to be recovered along side the services!

Haha, The Whats a SQL team sounds a lot like my day job!! Good one! In what ways do you utilize Visual Studio? I'd love to hear more...

Thanks! DR is a big process - and I get the fact that it's great you haven't had to do it! That said, there's a small part of me that gets excited and wants to just initiate the process (without the disaster of course)