{"id":603,"date":"2011-02-24T07:03:00","date_gmt":"2011-02-24T07:03:00","guid":{"rendered":"\/blogs\/paul\/post\/Better-together-the-importance-of-great-inter-team-relationships.aspx"},"modified":"2020-12-31T13:27:36","modified_gmt":"2020-12-31T21:27:36","slug":"better-together-the-importance-of-great-inter-team-relationships","status":"publish","type":"post","link":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/","title":{"rendered":"Better together &#8211; the importance of great inter-team relationships"},"content":{"rendered":"<p>\n<font face=\"verdana,geneva\" size=\"2\">Back at the end of January I kicked off a survey about the relationship between your DBA and dev teams. See <\/font><a href=\"https:\/\/www.sqlskills.com\/blogs\/paul\/survey-inter-team-relationships\/\"><font face=\"verdana,geneva\" size=\"2\">here<\/font><\/a><font face=\"verdana,geneva\" size=\"2\"> for the survey. <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">Here are the results: <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">&nbsp;<img decoding=\"async\" src=\"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg\" alt=\"\" \/> <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">The 22 Other values are: <\/font>\n<\/p>\n<ul>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">5 x The devs are great &#8211; it&#39;s the apps and the process that suck. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">4 x It depends on the development team. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">3 x I&#39;m the team lead and the DBA. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">2 x It&#39;s fine with the internal developers, but the consultants&#8230; not so much. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">2 x It&#39;s non-existent. Management does not have the DBA and dev team work together until there is an issue. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">1 x Essentially non-existant, between all groups: Infrastructure, DEV, DBA. Management has no interest in fixing it. Total crap gets moved to prod all the time, DBA&#39;s are the bad guys cause I&#39;ve stopped the practice of moving db side &quot;things&quot; into prod without testing. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">1 x It is spread out across country, DEV team think they are gods, what&#39;s a DBA? <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">1 x The DBA\/Dev relationship is good, it&#39;s the DBA\/Vendor relationship that sucks because vendor apps suck! <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">1 x The dev team have no clue what Data Architecture is all about 1The dev team is learning. Getting better all the time. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">1 x We are a small Admin team supporting scores of development teams. The teams are very segregated so relationships are very weak. <\/font>\n\t<\/div>\n<\/li>\n<\/ul>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">A very interesting variety of situations and views. Good to see that the majority of people are experiencing good relations between teams (answers 1 + 2 + 7 + 8 = 59%). <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">Here&#39;s a comment from the original post that sums up what I see a lot of the time when first working with clients: <\/font>\n<\/p>\n<blockquote>\n<p>\n\t<font face=\"verdana,geneva\"><font size=\"2\"><em>The developers think the DBAs are a bunch of idle boneheads, and the DBAs think the developers are a bunch of cowboys with little regard for the availability of the live servers.<\/em> <\/font><\/font>\n\t<\/p>\n<\/blockquote>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">Strong words, which demonstrate a fundamental lack of understanding about what the various teams do. That is very often the root cause of all the animosity between teams &#8211; not understanding the goals and motivations of the other team. For instance, a dev team is often under a lot of pressure to get the next release finished and put into production. A DBA team needs to preserve the availability and performance characteristics of the production system. These two goals are often at odds as the dev team wants to throw code over the wall and get it deployed, whereas the DBA team wants the code to be tested to ensure it will not compromise the production system in any way.<\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">There&#39;s also the case of those who answered #6 &#8211; one guy who&#39;s the problem between the teams. This could be someone in an architect or lead developer role, who has a lot of experience, but maybe some misconceptions, who has a domineering personality and is always right &#8211; no matter who is trying to show them that they are in fact incorrect. We&#39;ve never come across this person during our consulting work, oh no. :-)<\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">How do you work towards solving these problems? <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">Education. <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">It&#39;s no good just complaining and blaming each other when things don&#39;t go well. You need to have the other team understand *why* your team does what it does, *why* it&#39;s concerned about certain things, and *why* it operates under the pressures it does. I have a lot of experience managing development and program management teams and managing the relationships between the dev teams and the test teams, the dev teams and the build teams, the dev teams and the program management teams &#8211; so I&#39;m speaking from experience here. <\/font>\n<\/p>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">Last year in London we did a 1-day&nbsp;workshop where the focus was bridging the gap between development and production. We highlighted a bunch of problems we&#39;ve seen over the years and how some education could have helped. Here are some of the takeaways people had from the day: <\/font>\n<\/p>\n<ul>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Avoiding known design anti-patterns &#8211; don&#39;t repeat mistakes that others have made. Once you find a performance problem, give feedback on the design anti-pattern that caused it to everyone involved. A great example of this is thinking that single-column non-clustered indexes on every table column will be useful. There are some great posts and books about SQL anti-patterns, such as <\/font><a href=\"https:\/\/www.amazon.com\/SQL-Antipatterns-Programming-Pragmatic-Programmers\/dp\/1934356557\"><font face=\"verdana,geneva\" size=\"2\">this one<\/font><\/a><font face=\"verdana,geneva\" size=\"2\">. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Prototype and test design strategies &#8211; it&#39;s imperative that the developers have a test system that reproduces production workloads to the extent that proper scalability and load testing can be performed; otherwise it&#39;s not going to work in production. I see this over and over. It&#39;s also very important that developers and architects understand the ramifications of data type and schema design choices on the operational aspects of SQL Server (for instance, a LOB column in a table prevents online index operations on the clustered index). <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Workload analysis and performance base-lining &ndash; nothing allows you to identify that a new set of code has a problem faster than having a performance baseline, and monitoring so you can easily identify that the latest code change caused a performance change. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Troubleshooting to identify problems rather than throwing&nbsp;hardware at the problem &#8211; it&#39;s always better to find the root cause of a problem rather than trying to work around it with bigger iron or faster disks. You&#39;ll eventually run into the problem again. A good example is writing a query&nbsp;that is&nbsp;non-SARGable and requires an index or table scan. I blogged about this recently <\/font><a href=\"https:\/\/www.sqlskills.com\/blogs\/paul\/adventures-in-query-tuning-non-seekable-where-clause-expressions\/\"><font face=\"verdana,geneva\" size=\"2\">here<\/font><\/a><font face=\"verdana,geneva\" size=\"2\"> and many others have too. Implicit conversions are another great example &#8211; Jonathan has a great blog post about finding them&nbsp;<\/font><a href=\"http:\/\/sqlblog.com\/blogs\/jonathan_kehayias\/archive\/2010\/01\/08\/finding-implicit-column-conversions-in-the-plan-cache.aspx\"><font face=\"verdana,geneva\" size=\"2\">here<\/font><\/a><font face=\"verdana,geneva\" size=\"2\">. <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Build trust and partnership between teams &ndash; success is not one-sided and both teams look bad when an application\/project fails. A company with teams at odds will suffer. <\/font>\n\t<\/div>\n<\/li>\n<li><font face=\"verdana,geneva\" size=\"2\">Consistent post-mortems and &ldquo;lessons-learned&rdquo; from problems and mistakes rather than laying blame &#8211; being able to say mea culpa and proposing changes will elevate you above your peers whether you&#39;re a dev or a DBA. Just remember that if it&#39;s someone else&#39;s fault, constructive criticism needs to be well-phrased to be well-received. Don&#39;t make it personal.<\/font><\/li>\n<\/ul>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">And the one we stressed the most was: <\/font>\n<\/p>\n<ul>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Work to cross-train and educate both teams for best practices <\/font>\n\t<\/div>\n<\/li>\n<\/ul>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">This is the most powerful way to foster relationships between teams in my experience &#8211; offering to educate the other team on, say, one issue a week. This will show them that you&#39;re willing to put skin in the game (and hopefully they&#39;ll reciprocate) and in the long-term it will save&nbsp;you time. And it&#39;s a great way to show initiative and that you&#39;re a team player&nbsp; and motivator to your management. Some ideas for you on this: <\/font>\n<\/p>\n<ul>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">After a post-mortem, put together a list of links to blog posts and articles that explain facets of the problem and how to identify and or avoid it <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Organize a weekly self-study group that involves both teams. Use online material like our <\/font><a href=\"https:\/\/www.sqlskills.com\/t_mcmvideos.asp\"><font face=\"verdana,geneva\" size=\"2\">MCM prep videos<\/font><\/a><font face=\"verdana,geneva\" size=\"2\"> as a base. Management will love this, and people will almost feel compelled to be part of it, rather than showing management that they don&#39;t care about working better together. Even the nay-sayers will eventually see the benefit and come around. Persevere! <\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Get the team leads together to voice concerns and clear the air in a pre-agreed no-offense-will-be-taken closed-door meeting. You may be surprised at what lingering misconceptions, grudges, and misunderstandings can be cleared up by letting people vent and clearing the air.<\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font size=\"2\">Bring in an outside consultant who knows what they&#39;re talking about to be an independent voice of reason with no political baggage for either team. We get asked to do this every so often &#8211; it can be challenging but very effective, especially for the &quot;there&#39;s this one guy&quot; problems where no-one can convince them, or wants to publicly stand up to them. Often helping the person see the light and think they&#39;ve made the leap themselves is the best way forward &#8211; which can be hard to do from within the team, but a lot easier as an outsider, where we don&#39;t care about a position in the company pecking-order.<\/font>\n\t<\/div>\n<\/li>\n<li>\n<div>\n\t<font face=\"verdana,geneva\" size=\"2\">Send one dev and one DBA to a training class where they can both learn and bring back the learning to the teams with the two perspectives. Of all the classes we teach, the <\/font><a href=\"https:\/\/www.sqlskills.com\/t_immersioninternalsdesign.asp\"><font face=\"verdana,geneva\" size=\"2\">Internals and Performance<\/font><\/a><font face=\"verdana,geneva\" size=\"2\"> class is the best for this.<\/font>\n\t<\/div>\n<\/li>\n<\/ul>\n<p>\n<font face=\"verdana,geneva\" size=\"2\">To summarize, a bad working environment is toxic. You can fix it. It&#39;ll take some effort on your part but the pay-off is really worthwhile. And there are lots of resources out there to help you out.<\/font>\n<\/p>\n<p>\n<font size=\"2\">What are you waiting for?<\/font><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Back at the end of January I kicked off a survey about the relationship between your DBA and dev teams. See here for the survey. Here are the results: &nbsp; The 22 Other values are: 5 x The devs are great &#8211; it&#39;s the apps and the process that suck. 4 x It depends on [&hellip;]<\/p>\n","protected":false},"author":5,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[44,91],"tags":[],"class_list":["post-603","post","type-post","status-publish","format-standard","hentry","category-general","category-surveys"],"yoast_head":"<!-- This site is optimized with the Yoast SEO plugin v26.5 - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Better together - the importance of great inter-team relationships - Paul S. Randal<\/title>\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.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Better together - the importance of great inter-team relationships - Paul S. Randal\" \/>\n<meta property=\"og:description\" content=\"Back at the end of January I kicked off a survey about the relationship between your DBA and dev teams. See here for the survey. Here are the results: &nbsp; The 22 Other values are: 5 x The devs are great &#8211; it&#039;s the apps and the process that suck. 4 x It depends on [&hellip;]\" \/>\n<meta property=\"og:url\" content=\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/\" \/>\n<meta property=\"og:site_name\" content=\"Paul S. Randal\" \/>\n<meta property=\"article:published_time\" content=\"2011-02-24T07:03:00+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2020-12-31T21:27:36+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg\" \/>\n<meta name=\"author\" content=\"Paul Randal\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Paul Randal\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"7 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/\",\"name\":\"Better together - the importance of great inter-team relationships - Paul S. Randal\",\"isPartOf\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg\",\"datePublished\":\"2011-02-24T07:03:00+00:00\",\"dateModified\":\"2020-12-31T21:27:36+00:00\",\"author\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce\"},\"breadcrumb\":{\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg\",\"contentUrl\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Better together &#8211; the importance of great inter-team relationships\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#website\",\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/\",\"name\":\"Paul S. Randal\",\"description\":\"In Recovery...\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce\",\"name\":\"Paul Randal\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g\",\"caption\":\"Paul Randal\"},\"sameAs\":[\"http:\/\/3.209.169.194\/blogs\/paul\"],\"url\":\"https:\/\/www.sqlskills.com\/blogs\/paul\/author\/paul\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"Better together - the importance of great inter-team relationships - Paul S. Randal","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.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/","og_locale":"en_US","og_type":"article","og_title":"Better together - the importance of great inter-team relationships - Paul S. Randal","og_description":"Back at the end of January I kicked off a survey about the relationship between your DBA and dev teams. See here for the survey. Here are the results: &nbsp; The 22 Other values are: 5 x The devs are great &#8211; it&#39;s the apps and the process that suck. 4 x It depends on [&hellip;]","og_url":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/","og_site_name":"Paul S. Randal","article_published_time":"2011-02-24T07:03:00+00:00","article_modified_time":"2020-12-31T21:27:36+00:00","og_image":[{"url":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg","type":"","width":"","height":""}],"author":"Paul Randal","twitter_misc":{"Written by":"Paul Randal","Est. reading time":"7 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/","url":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/","name":"Better together - the importance of great inter-team relationships - Paul S. Randal","isPartOf":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#website"},"primaryImageOfPage":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage"},"image":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage"},"thumbnailUrl":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg","datePublished":"2011-02-24T07:03:00+00:00","dateModified":"2020-12-31T21:27:36+00:00","author":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce"},"breadcrumb":{"@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/"]}]},{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#primaryimage","url":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg","contentUrl":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-content\/uploads\/2011\/2\/teamrelationship.jpg"},{"@type":"BreadcrumbList","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/better-together-the-importance-of-great-inter-team-relationships\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/www.sqlskills.com\/blogs\/paul\/"},{"@type":"ListItem","position":2,"name":"Better together &#8211; the importance of great inter-team relationships"}]},{"@type":"WebSite","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#website","url":"https:\/\/www.sqlskills.com\/blogs\/paul\/","name":"Paul S. Randal","description":"In Recovery...","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/www.sqlskills.com\/blogs\/paul\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/ffcec826c18782e1e0adf173826a7fce","name":"Paul Randal","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/www.sqlskills.com\/blogs\/paul\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/0b6a266bba2f088f2551ef529293001bd73bf026bc1908b9866728c062beeeb6?s=96&d=mm&r=g","caption":"Paul Randal"},"sameAs":["http:\/\/3.209.169.194\/blogs\/paul"],"url":"https:\/\/www.sqlskills.com\/blogs\/paul\/author\/paul\/"}]}},"_links":{"self":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts\/603","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/users\/5"}],"replies":[{"embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/comments?post=603"}],"version-history":[{"count":0,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/posts\/603\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/media?parent=603"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/categories?post=603"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.sqlskills.com\/blogs\/paul\/wp-json\/wp\/v2\/tags?post=603"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}