{"id":4367,"date":"2016-07-19T23:29:00","date_gmt":"2016-07-19T23:29:00","guid":{"rendered":"https:\/\/209.235.70.100\/?p=4367"},"modified":"2022-09-22T14:23:54","modified_gmt":"2022-09-22T14:23:54","slug":"the-dba-best-practices-series-part-3-reducing-organizational-risk","status":"publish","type":"post","link":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/","title":{"rendered":"The DBA Best Practices Series Part 3- Reducing Organizational Risk"},"content":{"rendered":"\n<p>We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that if you want to be viewed as a strategic resource in your organization, being a technical expert isn\u2019t enough.&nbsp; Because of the trade you have chosen, the DBA position provides you with an excellent opportunity to play a more strategic role in your organization.&nbsp;In the&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/live-rdx-blog.pantheonsite.io\/the-dba-best-practices-series-becoming-a-strategic-resource-not-just-a-utility-provider\" target=\"_blank\">first installment<\/a>, we discussed the business value drivers that all organizations share:&nbsp; reduce costs, generate revenue, improve quality and reduce risk. The&nbsp;<a rel=\"noreferrer noopener\" href=\"https:\/\/live-rdx-blog.pantheonsite.io\/the-dba-best-practices-series-maximizing-your-organizations-database-technology-investment\" target=\"_blank\">second article<\/a>&nbsp;of the series focused on how you can reduce your organization\u2019s cost of doing business by ensuring they fully maximize their database investment. Let\u2019s move forward with our best practices series by talking about how DBAs can reduce organizational risk. &nbsp;Risk management is the strategy of identifying, analyzing and prioritizing potential threats to the business and is often used as the foundation for business continuity and disaster recovery strategies. &nbsp;But risks that organizations, their IT departments and DBA units in particular face are far more wide-ranging than just local and regional disasters. IT risk management is a well-developed science with various methodologies available to personnel who have dedicated their careers to this profession. &nbsp;Much of the focus is on security. We\u2019ll discuss reducing the risk of unauthorized data access in an upcoming article, but there are daily operational risks, in addition to security risks, that DBAs face on a daily basis. Let\u2019s identify some of the very basic risks that DBAs face on a daily basis:<\/p>\n\n\n\n<ul><li>Ensuring critical database-driven business application availability<\/li><li>Preventing and reducing impact of processing errors<\/li><li>Ensuring regulatory compliance<\/li><\/ul>\n\n\n\n<p>In this article, let\u2019s focus on availability and preventing\/reducing impact of processing errors. In upcoming articles in this series on risk reduction, we\u2019ll focus on database security and regulatory compliance.&nbsp;<strong>Critical database-driven application availability&nbsp;<\/strong>Computer professionals, by the very essence of their job descriptions, are the protectors of their organization\u2019s core data assets. They are tasked with ensuring key data stores are continuously available.&nbsp; However, ensuring that data is available on a 24 x 7 basis is a wonderfully complex task.&nbsp; Hardware failures, software problems, user errors and disasters all combine to make many technicians lie awake nights thinking about whether their applications will be continuously available. When a mission-critical application becomes unavailable, it can threaten the survivability of the organization.&nbsp; The financial impact of downtime is not the only issue that faces companies that have critical application failures.&nbsp; Loss of customer goodwill, bad press, idle employees and legal penalties (lawsuits, fines, etc.), must also be considered. It is up to the database administrator to recommend and implement technical solutions that deal with these unforeseen \u201ctechnology disruptions.\u201d &nbsp;Modern database systems are gaining features to help avoid downtime altogether by enabling change, optimization and management tasks to be performed while databases remain online. It is up to the IT support organization to understand and implement these features to reduce the amount of downtime required to perform administrative activities.&nbsp;<strong>Proactive Monitoring and Administration&nbsp;<\/strong>Daily support requests and problem solving often overwhelm IT groups.&nbsp; Understaffing, over-commitment to supporting new and legacy applications, lack of repeatable processes and budgetary constraints are the most common causes of IT professionals being reactive instead of proactive. The reactive IT professional can be compared to a firefighter; they resolve problems only after the problem occurs.&nbsp; The biggest problems garner the most attention. Their time is dominated by these firefighting activities, reducing the amount of time they are able to spend implementing the processes and procedures required to switch their mode from reactive firefighter to proactive problem prevention. Proactively monitoring your environments doesn\u2019t mean \u201cset it and forget it.\u201d &nbsp;The goal of your monitoring activities should be to proactively predict, analyze and prevent database availability and performance problems before they occur. &nbsp;Monitoring is an activity that you need to spend dedicated time on. There are numerous monitoring products to choose from.&nbsp; The market provides a wide variety of options from open source to commercial versions offered by big name vendors.&nbsp; The decision becomes budgetary. &nbsp;How much is your organization willing and able to spend on a monitoring solution?&nbsp; Once that decision is made, it is your responsibility as the DBA to fully leverage the product\u2019s capabilities. Once those products are installed, there are numerous websites that will assist you in selecting the appropriate metrics to evaluate. The advice that I have is to establish a base set of monitors that evaluate general, industry recommended performance and availability metrics. &nbsp;As stated, those metric recommendations are easily found.&nbsp; Not only will you find the metrics to monitor, you\u2019ll also find numerous tips, tricks and homegrown scripts for both open source and commercial products that will jumpstart the process. &nbsp;After installation, the key is to \u201cmonitor the monitors.\u201d &nbsp;The challenge to setting thresholds is to balance chatter reduction (unwarranted alerts) with adequate forewarning that an unfortunate event is going to occur. Each application has a unique workload; the goal is to customize the thresholds accordingly. &nbsp;Start with the base threshold setting and tailor them to each application\u2019s workload.&nbsp;<strong>Change Management&nbsp;<\/strong>Industry analysts estimate that as much as 80 percent of application failures can be attributed to human error. &nbsp; Database administrators usually support different business units with each unit having their own set of unique procedural requirements. Formalizing and documenting the change request process minimizes the potential for miscommunication between the business units, application development areas and the database administration unit. Standardized communication practices are a key ingredient of a trouble-free application environment.&nbsp;&nbsp; Effective communication ensures that there are no \u201csurprises\u201d when a change is implemented in production. If your organization doesn\u2019t have a formal change request process in place (and many shops don\u2019t), create your own! There are dozens of change management and source code versioning tools available on the market today. The prices can range from thousands to tens of thousands of dollars. Although I highly recommend these types of products, I wouldn\u2019t let the lack of having one prevent me from formalizing the change management process. Do the best with what you have. Be creative and focus on procedural enforcement that results in high-quality implementations and not \u201coh woe is me, I have no tools.\u201d From creating a single index to the implementation of a complex, multi-tier database-driven application architecture, good communication is absolutely critical during the change management process.&nbsp;<strong>Change Management Meetings<\/strong>&nbsp;If you read some of my earlier articles, you know I&#8217;m a proponent of constant communication between all units that are involved in the change management process. Here at RDX, we make sure we attend as many of our customers&#8217; change management meetings as we can. If it&#8217;s a database change, we want to be there to discuss it. How often should you hold these change management meetings? As often as you implement objects in production. If your organization makes changes to production environments on a daily basis, the meetings should be held daily. This is not as big of an imposition on your time as you may think. We provide remote database services for several very large organizations that have these change management meetings on a daily basis. The process takes about 15 to 20 minutes. It&#8217;s not a lot of time spent to ensure that everyone knows what is happening. To shorten the amount of time these meetings consume and to make them as productive as possible, the following discussion items should be a standard part of the meeting&#8217;s agenda:<\/p>\n\n\n\n<ul><li>Application name being changed<\/li><li>Date and time change will be implemented<\/li><li>Change description<\/li><li>Potential business impact if the changes don&#8217;t go as expected (include both units affected and how they will be affected)<\/li><li>Backoff procedures<\/li><li>Requestor<\/li><li>Tested by<\/li><\/ul>\n\n\n\n<p><strong>Repeatable Processes&nbsp;<\/strong>Documenting processes, procedures and best practices is a task that is often considered to be boring and mundane. Most DBAs would rather perform virtually any other activity than sit in front of a screen using a word processor. As a result, creating documentation is often postponed until the DBA has a little free time to kill. Today\u2019s database administration units are operating with smaller staffs, tighter budgets and ever-increasing workloads. The end result is that the documentation is either never created or created and not kept current. But a robust detailed documentation library creates an environment that is less complex, less error-prone, reduces the amount of time DBAs spend learning new database environments and reduces the overall time spent on day-to-day support activities. DBAs are able to spend more time administering the environment than finding the objects they are trying to support. Repetition, even though it can be boring, is the foundation for a high quality support environment. If the scripts and administrative process worked correctly the first time, chances are they will continue to work correctly in the future.&nbsp;<strong>Highly Available Architectures&nbsp;<\/strong>Building HA architectures is, once again, mainly a factor of cost, like mostly everything else in this profession. How much money is your organization willing, and able, to spend on highly available systems? All factors must be considered, not just hardware and software purchase costs and maintenance agreements. DBAs must all include training and labor hours required to administer the highly available system. Your job as a DBA is to present the options with your best cost estimations to management then assume full ownership of the quality of the chosen architecture.&nbsp;<strong>Recoverability&nbsp;<\/strong>When an unfortunate event does occur, do you have the correct components in place to ensure that your systems can be brought back to a usable state as quickly as possible? Databases can become unavailable for a variety of reasons: hardware failures, database software bugs, programs running haywire, changing too much data, too little data or changing it incorrectly. Your job is to ensure that your database environment is architected to successfully meet all challenges. Understand the recovery features provided by the database products you support. &nbsp;For example, not only can you roll changes forward in Oracle, the product also provides features to allow you to roll changes back. When I was consulting, I showed up early on my first day at a customer site. &nbsp;During my introduction they told me that key members of their DBA team were unavailable as they were preparing to restore a critical database to perform a point-in-time recovery. &nbsp;I asked if I could sit in, found that the restore wasn\u2019t needed and that Oracle would be able to \u201cundo\u201d the changes. When I announced that this was an option, by their comments, I knew the customer&#8217;s DBA team was thinking \u201che has no idea what he\u2019s talking about\u201d and I\u2019m thinking \u201cyou don\u2019t even know the recovery features your database provides.\u201d Most botched recoveries can be attributed to human error. Make sure all backups have proper retention periods, verify that all backups are executing correctly and run test recoveries on a regular basis. Don&#8217;t let missing backups of data files and\/or log files cause you to lose data. You don&#8217;t want to hear UNIX support say &#8220;The retention on that backup was supposed to be how long?&#8221; in the middle of a recovery. COMMUNICATE with others who are responsible for all other pieces of the recovery &#8220;pie&#8221; (system admins, operators) on a regular basis to ensure you have everything you need to recover a crashed database. Pick a database, identify the backup output files and verify that they are available when you need them. Remember, YOU are the IT professional who is ultimately responsible for ensuring that your organization&#8217;s databases can be quickly recovered. &nbsp;Not O\/S support, operations, application developers&#8230;. Don&#8217;t let your recovery skills get rusty. The more test recoveries you do the easier the production recoveries become. If you are a senior-level DBA, make sure you keep the junior folks on their toes. I have never personally seen the database make a mistake during the recovery process. That leaves incomplete backups and DBA error as the most likely causes of &#8220;good recoveries gone bad.&#8221; RELAX and Plan Your Attack. When you are notified of a database failure, take a deep breath and relax. Don&#8217;t immediately begin to paste the database back together without a plan. Create a recovery plan, put it on paper, have others review it if you can, and then execute it. You shouldn&#8217;t be trying to determine what the next step is in the middle of the recovery process. I will plan my attack on paper for all recoveries, no matter how simple they are. We\u2019ll continue our DBA Best Practices series in the next article in which we&#8217;ll discuss database security and regulatory compliance. &nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"","protected":false},"author":114,"featured_media":4341,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"acf":[],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v21.7 (Yoast SEO v21.7) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>The DBA Best Practices Series Part 3- Reducing Organizational Risk - Navisite<\/title>\n<meta name=\"description\" content=\"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"The DBA Best Practices Series Part 3- Reducing Organizational Risk\" \/>\n<meta property=\"og:description\" content=\"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\" \/>\n<meta property=\"og:site_name\" content=\"Navisite\" \/>\n<meta property=\"article:published_time\" content=\"2016-07-19T23:29:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2022-09-22T14:23:54+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/01\/RDX_Office_Warrendale_3.jpg\" \/>\n\t<meta property=\"og:image:width\" content=\"815\" \/>\n\t<meta property=\"og:image:height\" content=\"463\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/jpeg\" \/>\n<meta name=\"author\" content=\"Megan Ferringer\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:creator\" content=\"@navisite\" \/>\n<meta name=\"twitter:site\" content=\"@navisite\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Megan Ferringer\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"10 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#article\",\"isPartOf\":{\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\"},\"author\":{\"name\":\"Megan Ferringer\",\"@id\":\"https:\/\/www.navisite.com\/#\/schema\/person\/99bad6e33cc6d3ac27337400026e4a9f\"},\"headline\":\"The DBA Best Practices Series Part 3- Reducing Organizational Risk\",\"datePublished\":\"2016-07-19T23:29:00+00:00\",\"dateModified\":\"2022-09-22T14:23:54+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\"},\"wordCount\":2196,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\/\/www.navisite.com\/#organization\"},\"articleSection\":[\"Blog\"],\"inLanguage\":\"en-US\"},{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\",\"url\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\",\"name\":\"The DBA Best Practices Series Part 3- Reducing Organizational Risk - Navisite\",\"isPartOf\":{\"@id\":\"https:\/\/www.navisite.com\/#website\"},\"datePublished\":\"2016-07-19T23:29:00+00:00\",\"dateModified\":\"2022-09-22T14:23:54+00:00\",\"description\":\"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that\",\"breadcrumb\":{\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.navisite.com\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"The DBA Best Practices Series Part 3- Reducing Organizational Risk\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.navisite.com\/#website\",\"url\":\"https:\/\/www.navisite.com\/\",\"name\":\"Navisite\",\"description\":\"Elevate Your Cloud Journey\",\"publisher\":{\"@id\":\"https:\/\/www.navisite.com\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.navisite.com\/?s={search_term_string}\"},\"query-input\":\"required name=search_term_string\"}],\"inLanguage\":\"en-US\"},{\"@type\":\"Organization\",\"@id\":\"https:\/\/www.navisite.com\/#organization\",\"name\":\"Navisite\",\"url\":\"https:\/\/www.navisite.com\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.navisite.com\/#\/schema\/logo\/image\/\",\"url\":\"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/02\/logo.svg\",\"contentUrl\":\"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/02\/logo.svg\",\"width\":1,\"height\":1,\"caption\":\"Navisite\"},\"image\":{\"@id\":\"https:\/\/www.navisite.com\/#\/schema\/logo\/image\/\"},\"sameAs\":[\"https:\/\/twitter.com\/navisite\",\"https:\/\/www.instagram.com\/navisite\/\",\"https:\/\/www.linkedin.com\/company\/navisite\"]},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.navisite.com\/#\/schema\/person\/99bad6e33cc6d3ac27337400026e4a9f\",\"name\":\"Megan Ferringer\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.navisite.com\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/www.navisite.com\/wp-content\/uploads\/2021\/02\/IMG-0529-150x150.jpg\",\"contentUrl\":\"https:\/\/www.navisite.com\/wp-content\/uploads\/2021\/02\/IMG-0529-150x150.jpg\",\"caption\":\"Megan Ferringer\"},\"description\":\"Megan is the Content Marketing Manager at Navisite with more than 10 years of experience helping brands discover and tell their stories. From working at a global non-profit organization to boutique marketing agencies in Chicago, she champions the power of storytelling across all industries.\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"The DBA Best Practices Series Part 3- Reducing Organizational Risk - Navisite","description":"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/","og_locale":"en_US","og_type":"article","og_title":"The DBA Best Practices Series Part 3- Reducing Organizational Risk","og_description":"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that","og_url":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/","og_site_name":"Navisite","article_published_time":"2016-07-19T23:29:00+00:00","article_modified_time":"2022-09-22T14:23:54+00:00","og_image":[{"width":815,"height":463,"url":"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/01\/RDX_Office_Warrendale_3.jpg","type":"image\/jpeg"}],"author":"Megan Ferringer","twitter_card":"summary_large_image","twitter_creator":"@navisite","twitter_site":"@navisite","twitter_misc":{"Written by":"Megan Ferringer","Est. reading time":"10 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#article","isPartOf":{"@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/"},"author":{"name":"Megan Ferringer","@id":"https:\/\/www.navisite.com\/#\/schema\/person\/99bad6e33cc6d3ac27337400026e4a9f"},"headline":"The DBA Best Practices Series Part 3- Reducing Organizational Risk","datePublished":"2016-07-19T23:29:00+00:00","dateModified":"2022-09-22T14:23:54+00:00","mainEntityOfPage":{"@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/"},"wordCount":2196,"commentCount":0,"publisher":{"@id":"https:\/\/www.navisite.com\/#organization"},"articleSection":["Blog"],"inLanguage":"en-US"},{"@type":"WebPage","@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/","url":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/","name":"The DBA Best Practices Series Part 3- Reducing Organizational Risk - Navisite","isPartOf":{"@id":"https:\/\/www.navisite.com\/#website"},"datePublished":"2016-07-19T23:29:00+00:00","dateModified":"2022-09-22T14:23:54+00:00","description":"We learned in previous articles that it takes more than just being a great technician to keep your customers happy.&nbsp; The theme of this series is that","breadcrumb":{"@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/www.navisite.com\/blog\/the-dba-best-practices-series-part-3-reducing-organizational-risk\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.navisite.com\/"},{"@type":"ListItem","position":2,"name":"The DBA Best Practices Series Part 3- Reducing Organizational Risk"}]},{"@type":"WebSite","@id":"https:\/\/www.navisite.com\/#website","url":"https:\/\/www.navisite.com\/","name":"Navisite","description":"Elevate Your Cloud Journey","publisher":{"@id":"https:\/\/www.navisite.com\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.navisite.com\/?s={search_term_string}"},"query-input":"required name=search_term_string"}],"inLanguage":"en-US"},{"@type":"Organization","@id":"https:\/\/www.navisite.com\/#organization","name":"Navisite","url":"https:\/\/www.navisite.com\/","logo":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.navisite.com\/#\/schema\/logo\/image\/","url":"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/02\/logo.svg","contentUrl":"https:\/\/www.navisite.com\/wp-content\/uploads\/2020\/02\/logo.svg","width":1,"height":1,"caption":"Navisite"},"image":{"@id":"https:\/\/www.navisite.com\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/twitter.com\/navisite","https:\/\/www.instagram.com\/navisite\/","https:\/\/www.linkedin.com\/company\/navisite"]},{"@type":"Person","@id":"https:\/\/www.navisite.com\/#\/schema\/person\/99bad6e33cc6d3ac27337400026e4a9f","name":"Megan Ferringer","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.navisite.com\/#\/schema\/person\/image\/","url":"https:\/\/www.navisite.com\/wp-content\/uploads\/2021\/02\/IMG-0529-150x150.jpg","contentUrl":"https:\/\/www.navisite.com\/wp-content\/uploads\/2021\/02\/IMG-0529-150x150.jpg","caption":"Megan Ferringer"},"description":"Megan is the Content Marketing Manager at Navisite with more than 10 years of experience helping brands discover and tell their stories. From working at a global non-profit organization to boutique marketing agencies in Chicago, she champions the power of storytelling across all industries."}]}},"publishpress_future_action":{"enabled":false,"date":"1970-01-01 00:00:00","action":"","terms":[],"taxonomy":"","browser_timezone_offset":0},"_links":{"self":[{"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/posts\/4367"}],"collection":[{"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/users\/114"}],"replies":[{"embeddable":true,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/comments?post=4367"}],"version-history":[{"count":2,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/posts\/4367\/revisions"}],"predecessor-version":[{"id":32355,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/posts\/4367\/revisions\/32355"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/media\/4341"}],"wp:attachment":[{"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/media?parent=4367"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/categories?post=4367"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.navisite.com\/wp-json\/wp\/v2\/tags?post=4367"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}