{"id":1161,"date":"2021-01-16T16:53:36","date_gmt":"2021-01-16T08:53:36","guid":{"rendered":"https:\/\/www.yohz.com\/blogs\/?p=1161"},"modified":"2021-01-16T16:58:59","modified_gmt":"2021-01-16T08:58:59","slug":"standards-and-audit-compliance-in-postgresql-databases","status":"publish","type":"post","link":"https:\/\/www.yohz.com\/blogs\/2021\/01\/16\/standards-and-audit-compliance-in-postgresql-databases\/","title":{"rendered":"Standards and audit compliance in PostgreSQL databases"},"content":{"rendered":"<p>In <a href=\"https:\/\/www.yohz.com\/dbdoc_details.htm\">DB Doc<\/a> 9, we made a couple of additions to our existing reports that help in ensuring compliance with company standards with regards to table and column definitions.<\/p>\n<p>At the database level, there is now a listing of <span style=\"text-decoration: underline;\">all the tables across all schemas<\/span>.\u00a0 This allows you to easily look for similarly named tables, and ensure that they conform to your naming standards.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1167\" src=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05.png\" alt=\"\" width=\"1085\" height=\"655\" srcset=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05.png 1085w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05-300x181.png 300w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05-1024x618.png 1024w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05-768x464.png 768w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit05-624x377.png 624w\" sizes=\"(max-width: 1085px) 100vw, 1085px\" \/><\/p>\n<p>Similarly, there is now a listing of all the <span style=\"text-decoration: underline;\">table columns across all schemas<\/span>.\u00a0 This allows you to easily ensure that the column naming conventions are consistent, and that the data types are also consistent for similar columns.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1169\" src=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07.png\" alt=\"\" width=\"1154\" height=\"655\" srcset=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07.png 1154w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07-300x170.png 300w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07-1024x581.png 1024w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07-768x436.png 768w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit07-624x354.png 624w\" sizes=\"(max-width: 1154px) 100vw, 1154px\" \/><\/p>\n<p>At the schema level, there is also a listing for all the columns in the schema.<\/p>\n<p><img loading=\"lazy\" decoding=\"async\" class=\"aligncenter size-full wp-image-1170\" src=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09.png\" alt=\"\" width=\"1292\" height=\"636\" srcset=\"https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09.png 1292w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09-300x148.png 300w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09-1024x504.png 1024w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09-768x378.png 768w, https:\/\/www.yohz.com\/blogs\/wp-content\/uploads\/2021\/01\/dbdoc_audit09-624x307.png 624w\" sizes=\"(max-width: 1292px) 100vw, 1292px\" \/><\/p>\n<h3>What can you do with these reports?<\/h3>\n<ul>\n<li>you get a quick overview of <span style=\"text-decoration: underline;\">all tables across all schemas in your entire database<\/span>, allowing you to <span style=\"text-decoration: underline;\">compare attributes<\/span> like naming convention, size, estimated rows, etc<\/li>\n<li>you get a quick overview of <span style=\"text-decoration: underline;\">all columns across the entire database and across all schemas<\/span>, allowing you to <span style=\"text-decoration: underline;\">easily check for compliance<\/span> with naming convention and data types\/domains<\/li>\n<li>your database administrators and developers get <span style=\"text-decoration: underline;\">a single point of reference of your database schema<\/span>, which can be updated as frequently required using DB Doc&#8217;s command line execution<\/li>\n<\/ul>\n<h3>Customizing the reports<\/h3>\n<p>By default, all the above 3 listings are included in the HTML, XML, CHM, PDF, and DOC reports.\u00a0 You can remove one or more of the above listings by simply omitting the relevant user defined values, as explained in the help file <a href=\"https:\/\/www.yohz.com\/help\/dbdoc\/customizing_your_pdf_reports.htm\">here<\/a>.<\/p>\n<p>You can also easily customize what is displayed in each of the listings using DB Doc&#8217;s advanced scripting and report template features.\u00a0 For e.g. you could include the index size in the table listing, or display the nullable and unique attributes in the column listing<\/p>\n<h3>Give DB Doc a try now<\/h3>\n<p>Download the installer <a href=\"https:\/\/www.yohz.com\/downloads\/dbdoc\/DBDocSetup.zip\">here<\/a> and see how DB Doc can help you generate accurate and timely database documentation in minutes.\u00a0 We have a walkthrough available <a href=\"https:\/\/www.yohz.com\/dbdoc_demo.htm\">here<\/a> to guide you for new users.<\/p>\n<div class=\"fcbkbttn_buttons_block\" id=\"fcbkbttn_left\"><div class=\"fcbkbttn_like \"><fb:like href=\"https:\/\/www.yohz.com\/blogs\/2021\/01\/16\/standards-and-audit-compliance-in-postgresql-databases\/\" action=\"like\" colorscheme=\"light\" layout=\"button\"  size=\"small\"><\/fb:like><\/div><div class=\"fb-share-button  \" data-href=\"https:\/\/www.yohz.com\/blogs\/2021\/01\/16\/standards-and-audit-compliance-in-postgresql-databases\/\" data-type=\"button\" data-size=\"small\"><\/div><\/div>","protected":false},"excerpt":{"rendered":"<p>In DB Doc 9, we made a couple of additions to our existing reports that help in ensuring compliance with company standards with regards to table and column definitions. At the database level, there is now a listing of all the tables across all schemas.\u00a0 This allows you to easily look for similarly named tables, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[6],"tags":[3],"_links":{"self":[{"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/posts\/1161"}],"collection":[{"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/comments?post=1161"}],"version-history":[{"count":4,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/posts\/1161\/revisions"}],"predecessor-version":[{"id":1173,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/posts\/1161\/revisions\/1173"}],"wp:attachment":[{"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/media?parent=1161"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/categories?post=1161"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.yohz.com\/blogs\/wp-json\/wp\/v2\/tags?post=1161"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}