<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">

<channel>

  <atom:link href="https://community.pyramidanalytics.com/rss/category/databases" rel="self" type="application/rss+xml"/>
  <title>Pyramid Analytics User Community&#32;Databases</title>
  <link>https://community.pyramidanalytics.com/category/databases/</link>
  <description>Pyramid Internal Databases
(The Application Repository)</description>
  <language>en-us</language>
<ttl>240</ttl>
  <item>
          <title>How to move the Pyramid repository location</title>
          <link>https://community.pyramidanalytics.com/t/g9h0clx/how-to-move-the-pyramid-repository-location</link>
          <description><![CDATA[<p>The following explains how to move the Pyramid repository location to another server if needed.</p>
<p>You first need to stop the services to change your Pyramid repository location.<br> Then back up your Database and restore it to the destined server.</p>
<p>For each Pyramid server in your deployment edit the&nbsp;<strong>config.ini</strong> file. Update "Dbhost" to point to the new repository server (see picture).</p>
<p>By default it can be found here&nbsp;c:\Program Files\Pyramid\config.ini and on Linux&nbsp; /opt/Pyramid/config.ini</p>
<p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/12270d61-e9b8-4118-95f9-8bec255c27e0/h/547.png" style="" width="297"></p>
<p>&nbsp;</p>
<p>If the username and password&nbsp; will stay the same, there is no need to do anything else. Otherwise, you will need to update the <strong>config.ini</strong> file&nbsp;with the new user and encrypted password(this applies if only one of them will change).<br> To accomplish&nbsp;it, follow this article:&nbsp;<a href="/t/p8h6cjg/how-to-update-the-pyramid-repository-credentials" rel="nofollow noopener noreferrer">How to update the Pyramid repository credentials</a>.</p>]]></description>
          <pubDate>Thu, 02 Feb 2023 20:21:42 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/g9h0clx/how-to-move-the-pyramid-repository-location</guid>
          <dc:creator>Liran Levi</dc:creator>
        </item>

      <item>
          <title>How to add a CData custom connector as a data source</title>
          <link>https://community.pyramidanalytics.com/t/60hs9tz/how-to-add-a-cdata-custom-connector-as-a-data-source</link>
          <description><![CDATA[<p>A step-by-step guide on how to add a&nbsp;<a href="https://www.cdata.com/" rel="nofollow noopener noreferrer" target="_blank">CData</a>&nbsp;custom connector as a data source.<br> &nbsp;</p>
<ol>
 <li>Download the Java JDBC driver for the data source you want to connect to.<br> (Click <a href="https://www.cdata.com/drivers/" rel="nofollow noopener noreferrer" target="_blank">here</a>&nbsp;for a complete list of the different data sources that CData supports) Run the installer to extract the JAR file.<br> <img alt="" src="https://pyramidanalytics.zendesk.com/attachments/token/mOakSjxoZDXuWDTx7d0yhI8BZ/?name=inlineImage.png" style="padding:0px"></li>
 <li>To&nbsp;see the list of connection properties you can use, open the CData jar using JAVA.<br> To do this:<br> Open a command prompt on the Pyramid server and point to the location of the extracted JAR file. <pre class="language-none"><code class="language-none">C:\Program&nbsp;Files\CData\CData&nbsp;JDBC&nbsp;Driver&nbsp;for&nbsp;Microsoft&nbsp;Dynamics&nbsp;CRM&nbsp;2022\lib</code></pre> And where JAVA is installed <pre class="language-none"><code class="language-none">"C:\Program&nbsp;Files\Pyramid\java\bin\java.exe"&nbsp;-jar&nbsp;cdata.jdbc.dynamicscrm.jar</code></pre></li>
 <li>Fill in the connection properties that you want to use.<br> E.g. <p style="text-align:left"><img alt="" src="https://pyramidanalytics.zendesk.com/attachments/token/hr2TLjsLOP8HvCkyTfOLnwcCh/?name=inlineImage.png" style="padding:0px"></p> Once all details have been filled in, click on the "Test connection" button to make sure it works.<br> Then click on "Copy to Clipboard" to copy the connection string.<br> &nbsp;</li>
 <li>Go to custom connectors in Pyramid (admin&gt;data&gt;custom connectors)<br> and&nbsp;add a new one and upload the downloaded driver.<br> &nbsp;</li>
 <li>Paste in the connection string from the CData you just copied <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/29103714-3777-491a-9e9f-e83d504eab21/h/547.png" style="" width="1098"></p> CData RTK is a license key.<br> You'll need to contact <a href="https://www.cdata.com/" rel="nofollow noopener noreferrer" target="_blank">CData</a> and ask them for a trial license.<br> &nbsp;</li>
 <li>Change all parameters to a relevant name wrapped in curly brackets {} as shown below:<br> <img alt="" src="https://pyramidanalytics.zendesk.com/attachments/token/slS5fIqeqdmq7T5LEM6D19tZt/?name=inlineImage.png" style="padding:0px"><br> <br>The best practice is to use these name conventions as your parameters:<br> database, user, password, port, ip<br> This is not mandatory but preferred.<br> &nbsp;</li>
 <li>Click on apply and add the custom connector.<br> &nbsp;</li>
 <li>In Add Data Source, add the new data source like&nbsp;any other by filling out all the relevant connection details.<br> (admin&gt;data source) <p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/506621d8-c99c-4048-81d4-497d90a0ad9e/h/547.png" style="" width="1110"></p></li>
</ol>
<p>For more information about setting up the connectors, please see our <a href="https://help.pyramidanalytics.com/Content/Root/AdminClient/data%20sources/Custom%20Connectors.htm?Highlight=custom%20connectors" rel="nofollow noopener noreferrer" target="_blank">Help</a>.</p>
<p>For more information about the CData drivers and their documentation you can refer to this <a href="https://www.cdata.com/drivers/" rel="nofollow noopener noreferrer" target="_blank">link</a>, choose the driver you need, and then click docs as shown below:</p>
<p style="text-align:left"><img alt="" class="fb-img" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/2868c9ee-ead7-45f8-8ac4-3ae50e16bafa/h/547.png" style="" width="649"></p>]]></description>
          <pubDate>Mon, 26 Dec 2022 12:20:52 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/60hs9tz/how-to-add-a-cdata-custom-connector-as-a-data-source</guid>
          <dc:creator>Omer Ansher</dc:creator>
        </item>

      <item>
          <title>How to backup and restore a PostgreSQL database via DBeaver</title>
          <link>https://community.pyramidanalytics.com/t/h7hk07w/how-to-backup-and-restore-a-postgresql-database-via-dbeaver</link>
          <description><![CDATA[<p>This article discusses how to back up and restore your&nbsp;PostgreSQL database via DBeaver.&nbsp;</p>
<p>There is another way to do it via the windows command line, as described in this article:&nbsp;<a href="/t/1852k1/how-to-backup-and-restore-a-postgresql-database" rel="nofollow noopener noreferrer">How to Backup and Restore a PostgreSQL database</a>.</p>
<p><strong>Backup:</strong><br> First, go to your DBeaver application, and then-</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/118220f6-4718-41f6-82c5-0012f011243f/h/547.png" style=""><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/2741aee6-f3ad-480e-81c3-29662dbdda5f/h/547.png" style=""><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/5e2b6a97-614d-4f40-ba2b-704ab1bc6722/h/547.png" style=""></p>
<p><strong>Restore:</strong><br> First, create a new DB so you can restore to it the backup DB<br> <br><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/31b0766c-8816-4a80-b21a-c746bd81821d/547.png" style=""></p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/0d7be8bb-8f56-4cab-ad34-83c110e5f5d3/547.png" style=""></p>
<p>And then-</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/40669ca5-2b3e-43b5-8ab9-f23a5293d3f6/547.png" style="">&nbsp;<img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/ed803e8a-2537-4c26-9815-2a4dad465517/547.png" style="">&nbsp;</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/4a30469a-a32f-44d1-95db-74c517ff7248/547.png" style="">&nbsp;<img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/b70ce758-0ba8-4a3f-8ebf-1b8057259b3c/547.png" style="">&nbsp;&nbsp;</p>]]></description>
          <pubDate>Tue, 20 Jul 2021 12:56:00 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/h7hk07w/how-to-backup-and-restore-a-postgresql-database-via-dbeaver</guid>
          <dc:creator>Omer Ansher</dc:creator>
        </item>

      <item>
          <title>Creating a test environment from a production repository</title>
          <link>https://community.pyramidanalytics.com/t/35h808r/creating-a-test-environment-from-a-production-repository</link>
          <description><![CDATA[<p>The following article will cover <strong>PostgresSQL,&nbsp;</strong><strong>SQL, </strong>And <strong>Oracle&nbsp;</strong>databases.</p>
<h2>Postgres</h2>
<p>When using Postgres as the Pyramid repository, to create a copy of an existing environment, you first need to install Pyramid using the same version of the environment you are copying from, then replace the newly created repository with the backup taken from the existing environment.</p>
<p>The first step is to confirm the Pyramid version on&nbsp;the production environment.<br> You can get to it&nbsp;by&nbsp;clicking&nbsp;on your&nbsp;initials on the tab at the top right-hand side of the&nbsp;screen, as&nbsp;shown below.&nbsp;</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/fba4a49c-1bac-480a-bac3-4e4887b889b1/547.jpg" style=""></p>
<p>Here, we can see it's Pyramid version 2020.11.030.<br> In this case, we will run the installer version 2020.11.030 in our test environment.</p>
<p>When running the installer, we will choose a new internal repository or new remote repository &gt; PostgresSQL:</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/47dd028c-233e-41f7-94ef-32736da40098/547.jpg" style=""></p>
<p>After completing the installation, go back to the production environment and back up the repository.</p>
<p>To create the backup, run the following command in your production server:</p>
<pre class="language-shell"><code class="language-shell">"C:\Program&nbsp;Files\Pyramid\postgres\pgsql\bin\pg_dump.exe"&nbsp;-U&nbsp;pyramid&nbsp;-h&nbsp;localhost&nbsp;-p&nbsp;12130&nbsp;-F&nbsp;t&nbsp;-f&nbsp;C:\backup\pyramidDbBackup.tar&nbsp;Your_repo_name</code></pre>
<p>The default password for the DB will be the name of the DB with '!' after the word “pyramid”<br> <strong>example</strong>:&nbsp;DB name:pyramid123 password: pyramid!123<br> <br>The way to change the Postgres password via CMD is with the following commands, which need to run on the server running the Pyramid Postgres service.</p>
<pre class="language-shell"><code class="language-shell">1.&nbsp;cd&nbsp;C:\Program&nbsp;Files\Pyramid\postgres\pgsql\bin
2.&nbsp;set&nbsp;PGPASSWORD=CurrentPassowrd
3.&nbsp;psql&nbsp;-h&nbsp;localhost&nbsp;-d&nbsp;DB&nbsp;name&nbsp;-U&nbsp;pyramid&nbsp;-p&nbsp;12130&nbsp;-c&nbsp;"ALTER&nbsp;USER&nbsp;pyramid&nbsp;WITH&nbsp;PASSWORD&nbsp;'NewPassword';"</code></pre>
<p>To get your DB name, go to your pyramid folder and open the config.ini&nbsp;file.<br> There, under data, you will see the database, and this is the name of your DB.<br> <strong>NOTE</strong>:&nbsp;The path to your pyramid folder in Windows is C:\Program Files\Pyramid<br> and in Linux, it's - /opt/pyramid.<br> <br>If you&nbsp;want to update the password in the config, you need to use the maintenance tool.<br> See this article for more information:&nbsp;<a href="https://help.pyramidanalytics.com/Content/Root/Guides/installation/Main/System%20Maintenance.htm?Highlight=maintenance%20tool" rel="nofollow noopener noreferrer" target="_blank">Maintenance Tool</a><br> <br>Now copy the file to your Test environment and run the following command in the CMD to restore the database:</p>
<pre class="language-shell"><code class="language-shell">"C:\Program&nbsp;Files\Pyramid\postgres\pgsql\bin\pg_restore.exe"&nbsp;--clean&nbsp;-h&nbsp;localhost&nbsp;-p&nbsp;12130&nbsp;-U&nbsp;pyramid&nbsp;-d&nbsp;pyramid_repo&nbsp;C:\backup\pyramidDbBackup.tar</code></pre>
<p>The following article describes&nbsp;<a href="/t/h7hk07w/how-to-backup-and-restore-a-postgresql-database-via-dbeaver" rel="nofollow noopener noreferrer">How to back up and restore a PostgreSQL database via DBeaver</a>.<br> <br>After restoring has been completed, you'll need to truncate the server table by running the file you can download&nbsp;<a href="/media/download/36lwam/truncate%20tables.zip" rel="nofollow noopener noreferrer">here</a>&nbsp;or by connecting to the database via a 3rd party app.</p>
<p>After truncating the tables, restart all Pyramid services, wait a few minutes, and try to log in.</p>
<p><strong>NOTE</strong>: you will need to change the data sources so they won't point to production data sources.</p>
<p><strong>If you are using IMDB, you must copy the IMDATA folder from the production server.<br> The IMDATA folder is located in C:\Program Files\Pyramid\repository\imdata</strong></p>
<p>Ensure everything is working fine and all the reports can be opened without errors.</p>
<p>Now, if you restored the backup to a new instance, the following command should be run on cmd :</p>
<pre class="language-shell"><code class="language-shell">1.&nbsp;cd&nbsp;C:\Program&nbsp;Files\Pyramid\postgres\pgsql\bin
2.&nbsp;psql&nbsp;-h&nbsp;localhost&nbsp;-d&nbsp;DB&nbsp;name&nbsp;-U&nbsp;pyramid&nbsp;-p&nbsp;12130&nbsp;-c&nbsp;"CREATE&nbsp;EXTENSION&nbsp;IF&nbsp;NOT&nbsp;EXISTS&nbsp;""uuid-ossp"";"</code></pre>
<p>Or you can use a 3rd party app, like Dbeaver, to run it directly on the database:</p>
<pre class="language-shell"><code class="language-shell">CREATE&nbsp;EXTENSION&nbsp;IF&nbsp;NOT&nbsp;EXISTS&nbsp;"uuid-ossp"</code></pre>
<p style="text-align:start">The above is needed because the Pyramid installer uses this extension when running scripts to update the Pyramid database.<br> <strong>Note</strong>:&nbsp;The above command should NOT be run on a local Pyramid Postgres instance.</p>
<p style="text-align:start">&nbsp;</p>
<hr>
<h2>MS SQL Server and Oracle</h2>
<p>When using these DB's as a repository for Pyramid, the process is first to create a backup and then restore it in the destination, then install using the copy of the repository.</p>
<p>You will need the same Pyramid or higher Pyramid versions for SQL and Oracle databases.<br> For example, if you have Pyramid 2024.03.110, you can run installer build 2025.10.012.</p>
<p>The first step is to&nbsp;create a repository backup from the production environment and restore it on your SQL or Oracle&nbsp;test environment.</p>
<p>After you have restored the repository into your SQL or Oracle test environment, you can run the Pyramid installer and choose "Reuse Pre-existing Repository" &gt; Microsoft <strong>SQL </strong>Server Or <strong>Oracle</strong>.</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/1efb36bc-1b0a-4623-a5a0-2acefd288a0a/547.jpg" style=""></p>
<p>Point Pyramid to your SQL database:</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/9aaaab7e-a2a5-4a1a-b197-63d2dc37c076/547.jpg" style=""></p>
<p>Or Point Pyramid to your Oracle database:</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/0b81cad1-085a-462c-9296-adc45584685f/547.jpg" style=""></p>
<p>And finish the installation.</p>
<p>Log in to your test environment and make sure you can open the reports.</p>
<p><strong>Make sure to stop all the models and stop all publications.</strong></p>
<p>Once the test environment is working, you need to deactivate its license (admin console -&gt; licensing -&gt; deactivate instance), get the machine key(after reloading the page -&gt; new deployment -&gt; generate machine key), and send it to your account manager to get a test pyramid license.</p>
<p>Each pyramid environment must have its license and not use the same one as another environment.</p>]]></description>
          <pubDate>Tue, 29 Sep 2020 07:36:00 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/35h808r/creating-a-test-environment-from-a-production-repository</guid>
          <dc:creator>Liran Jorno</dc:creator>
        </item>

      <item>
          <title>Retrieving XMLA to analyze cube structure</title>
          <link>https://community.pyramidanalytics.com/t/m2sygk/retrieving-xmla-to-analyze-cube-structure</link>
          <description><![CDATA[<p>Below are instructions on how to get&nbsp;the cube structure (dimensions, hierarchies, measures…)</p>
<p>It can help the Pyramid development team debug&nbsp;cases where the query fails to get the cube metadata.<br> &nbsp;</p>
<p><strong>Steps:</strong></p>
<p>In Microsoft SQL Server Management Studio, connect to&nbsp;the analysis server&nbsp;for the relevant cube/model.</p>
<p>Run the below two&nbsp;XMLA queries,&nbsp;</p>
<p>Send the two queries results to the Pyramid support team for further analysis.<br> (Below is an example image)<br> <br>This is the first query to run:</p>
<blockquote>
 <p>&lt;Discover xmlns="urn:schemas-microsoft-com:xml-analysis"&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;RequestType&gt;DISCOVER_XML_METADATA&lt;/RequestType&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Restrictions&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;RestrictionList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ObjectExpansion&gt;ExpandObject&lt;/ObjectExpansion&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/RestrictionList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/Restrictions&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Properties&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;PropertyList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;CONTENT&gt;Data&lt;/CONTENT&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/PropertyList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/Properties&gt;</p>
 <p>&lt;/Discover&gt;</p>
</blockquote>
<p>Copy the first result in a notepad, to send it to us.<br> Now, In the result, please look for this segment:<br> &nbsp;</p>
<blockquote>
 <p>&lt;Database&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&lt;Name&gt;Pyramid Demo 2013&lt;/Name&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;ID&gt;Pyramid Demo 2013&lt;/ID&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;CreatedTimestamp&gt;2010-12-26T07:04:30&lt;/CreatedTimestamp&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;LastSchemaUpdate&gt;2013-12-03T07:46:23.46&lt;/LastSchemaUpdate&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;LastProcessed&gt;2015-09-01T11:12:36.416667&lt;/LastProcessed&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;State&gt;Processed&lt;/State&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;LastUpdate&gt;2019-03-31T15:34:31.616667&lt;/LastUpdate&gt;</p>
 <p>&lt;/Database&gt;</p>
</blockquote>
<p>The <strong><em>&lt;Name&gt;</em></strong> tag contains the name of the model you're trying to open.<br> The <strong><em>&lt;ID&gt;</em></strong> tag holds a value you'll need for the next query.<br> Take the value and use it in the <strong><em>&lt;DatabaseID&gt;</em></strong> tag of this next query and run it.<br> &nbsp;</p>
<blockquote>
 <p>&lt;Discover xmlns="urn:schemas-microsoft-com:xml-analysis"&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;RequestType&gt;DISCOVER_XML_METADATA&lt;/RequestType&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Restrictions&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;RestrictionList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;DatabaseID&gt;Pyramid Demo 2013&lt;/DatabaseID&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/RestrictionList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/Restrictions&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;Properties&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;PropertyList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;CONTENT&gt;Data&lt;/CONTENT&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/PropertyList&gt;</p>
 <p>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; &lt;/Properties&gt;</p>
 <p>&lt;/Discover&gt;</p>
</blockquote>
<p>Copy the second result in the notepad as well and send both results back to the Pyramid support team.</p>
<p>&nbsp;</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/bc1e686b-cc54-419f-a675-fdded151a002/547.jpg" style="" width="632"></p>]]></description>
          <pubDate>Mon, 27 Jul 2020 16:14:49 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/m2sygk/retrieving-xmla-to-analyze-cube-structure</guid>
          <dc:creator>Yakov Shaul</dc:creator>
        </item>

      <item>
          <title>Routine Content Backup Recommendations</title>
          <link>https://community.pyramidanalytics.com/t/6377lh/routine-content-backup-recommendations</link>
          <description><![CDATA[<p>The following are items we Recommend backing up periodically.<br> (Preferably Daily but it's up to you)</p>
<ol>
 <li>The <strong>database repository</strong>.<br> If you don't know where it is, browse to <em>HTTP://&lt;Your Pyramid Site&gt;/diagnostic</em>
  <ul>
   <li>If it's an SQL database, then use SQL Management studio to back it up.</li>
   <li>If you are using the local Postgres option for your repository,<br> see this article <a href="/t/1852k1/how-to-backup-and-restore-a-postgresql-database" rel="nofollow noopener noreferrer">here</a>&nbsp;on how to back it up.</li>
   <li>If you are using Oracle, then set up a backup job to do this.</li>
  </ul></li>
 <li>The general folder(used to store <strong>publications </strong>and <strong>printed content</strong>),<br> Found by default here:&nbsp;<em>C:\Program Files\Pyramid\repository\general <strong>*</strong></em><br> If you have more than one Pyramid server in your deployment, then back it up on all Pyramid servers.<br> &nbsp;</li>
 <li>The upload folder (used for ETL's, the Yellow app) that are based on <strong>Excel</strong> <strong>spreadsheets</strong>.<br> Found by default here:&nbsp;<em>C:\Program Files\Pyramid\repository\upload</em> <strong>*</strong><br> If you have more than one Pyramid server in your deployment, then back it up on all Pyramid servers.<br> &nbsp;</li>
 <li>If you’re using <strong>IMDB</strong>(In Memory database), then you should back up the created databases.<br> They can be found on the server running IMDB,<br> in the folder located here: <em>C:\Program Files\Pyramid\repository\imdata</em></li>
</ol>
<p><strong>* </strong>If any of the folder locations have been changed from within the config.ini file (C:\Program Files\Pyramid/config.ini), then these are the locations that should be backed up.</p>]]></description>
          <pubDate>Wed, 10 Apr 2019 06:26:35 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/6377lh/routine-content-backup-recommendations</guid>
          <dc:creator>Daniel</dc:creator>
        </item>

      <item>
          <title>How to hide Microsoft SQL databases that a user does not have access to</title>
          <link>https://community.pyramidanalytics.com/t/63byya/how-to-hide-microsoft-sql-databases-that-a-user-does-not-have-access-to</link>
          <description><![CDATA[<p>By default even if a user does not have access to an Microsoft SQL database they can still view it when logging into SQL Management studio.&nbsp;Therefore the same behavior will be seen in Pyramid when connecting to a SQL data source&nbsp;. If you want the users to only see the database that they have access to, then you can add edit the MS SQL role called "Public". Set the property "View any database" to "Deny". Now when a user logs in, they will only see the databases that they have access to.</p>
<p>1) Login to SQL Management studio and connect to your SQL instance.</p>
<p>Expand Security&gt;Server Roles&gt; and double click on the "Public" role</p>
<p><img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/d37b25f5-c78a-40f9-8583-018772a12712/547.jpg" style="" width="337"></p>
<p>2) Expand Servers and select your SQL instance. Then tick the box Deny for "View any database"<img alt="" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/867762a4-af97-48d2-af9b-8c2a1e298836/547.jpg" style="" width="632">Please note that there are other ways of doing this, or by just setting a deny view permission on specific databases. Lots more information on this topic can be found on the internet.&nbsp;</p>]]></description>
          <pubDate>Tue, 16 Oct 2018 07:18:03 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/63byya/how-to-hide-microsoft-sql-databases-that-a-user-does-not-have-access-to</guid>
          <dc:creator>Daniel</dc:creator>
        </item>

      <item>
          <title>How to backup and restore a PostgreSQL database</title>
          <link>https://community.pyramidanalytics.com/t/1852k1/how-to-backup-and-restore-a-postgresql-database</link>
          <description><![CDATA[<p>Before upgrading Pyramid, it is strongly recommended to back up the Pyramid repository database.</p>
<p>This article explains how to back up and restore a PostgreSQL repository database using the command line on Windows and Linux.</p>
<p><strong>Important for Pyramid 2025.11 and later:</strong> Pyramid no longer supports PostgreSQL 12 or earlier for its repository database. Customers previously using the bundled PostgreSQL 9.6 database must migrate to a supported PostgreSQL version before upgrading to Pyramid 2025.11 or later.</p>
<p>The migration guides use PostgreSQL 18, which is installed and managed separately from Pyramid. The standard PostgreSQL port is 5432, rather than the port 12130 used by the older bundled database.</p>
<p>For detailed migration instructions, see:</p>
<ul>
 <li><a href="/t/m1yjmxm/migrating-the-pyramid-database-from-postgresql-9-6-to-postgresql-18-windows" rel="nofollow noopener noreferrer"> Migrating PostgreSQL 9.6 to PostgreSQL 18 - Windows </a></li>
 <li><a href="/t/60yjmmq/migrating-the-pyramid-database-from-postgresql-9-6-to-postgresql-18-linux" rel="nofollow noopener noreferrer"> Migrating PostgreSQL 9.6 to PostgreSQL 18 - Linux </a></li>
</ul>
<h2>1. Identify the PostgreSQL Connection Details</h2>
<p>Before running any commands, identify the database name, host, port, username, and password.</p>
<p>These can be found in the Pyramid <strong>config.ini</strong> file, located in the Pyramid installation directory.</p>
<p><strong>Default Windows location:</strong></p>
<pre class="language-none"><code>C:\Program Files\Pyramid\config.ini</code></pre>
<p><strong>Default Linux location:</strong></p>
<pre class="language-none"><code>/opt/pyramid/config.ini</code></pre>
<p>Check the <strong>[data]</strong> section for the repository connection settings.</p>
<p><img alt="Pyramid repository database configuration" src="https://s3-us-west-2.amazonaws.com/media.forumbee.com/i/d0ae456a-6ea3-4775-afce-14bb686a4080/h/547.png" style="max-width:100%;height:auto;"></p>
<h3>Database Name and Password</h3>
<p>In modern Pyramid installations, the built-in PostgreSQL database name is normally generated automatically rather than using the older database name <strong>pyramidg2</strong>.</p>
<p>For installations using the default generated credentials, the database name starts with <strong>pyramid</strong> followed by an alphanumeric sequence.</p>
<p>The default database password is generated by inserting an exclamation mark (!) immediately after the word <strong>pyramid</strong>.</p>
<p><strong>Example:</strong></p>
<ul>
 <li>Database name: <code>pyramid2324f</code></li>
 <li>Username: <code>pyramid</code></li>
 <li>Password: <code>pyramid!2324f</code></li>
</ul>
<p>These values are examples only. Always verify the actual repository connection settings. If the password has been changed manually, use the configured password instead.</p>
<h3>PostgreSQL Port and Installation Location</h3>
<p>The connection settings depend on whether you are using the older bundled PostgreSQL database or a separately installed PostgreSQL server.</p>
<table>
 <thead>
  <tr>
   <th>Setting</th>
   <th>Older Bundled PostgreSQL</th>
   <th>Separately Installed PostgreSQL 18</th>
  </tr>
 </thead>
 <tbody>
  <tr>
   <td>Default port</td>
   <td>12130</td>
   <td>5432</td>
  </tr>
  <tr>
   <td>Windows PostgreSQL utilities</td>
   <td>C:\Program Files\Pyramid\postgres\pgsql\bin</td>
   <td>C:\Program Files\PostgreSQL\18\bin</td>
  </tr>
  <tr>
   <td>Database name</td>
   <td>Generated name</td>
   <td>Existing name retained during migration</td>
  </tr>
  <tr>
   <td>Username</td>
   <td>pyramid</td>
   <td>pyramid (if retained during migration)</td>
  </tr>
 </tbody>
</table>
<p><strong>Important:</strong> After migrating from bundled PostgreSQL to PostgreSQL 18, the database name, username, and password should remain unchanged if the documented migration procedure was followed.</p>
<p>The port will normally change from 12130 to 5432. Always confirm the actual value in <strong>config.ini</strong>, as installations may use a custom port.</p>
<p>On Linux, the PostgreSQL 18 executable location depends on the Linux distribution and installation method. Use the installed PostgreSQL 18 utilities, rather than assuming they are still located inside the Pyramid installation directory.</p>
<h2>2. Backing Up the PostgreSQL Database</h2>
<p>Use the PostgreSQL <strong>pg_dump</strong> utility to create a database backup.</p>
<p>The following examples use:</p>
<ul>
 <li>Database name: <code>pyramid2324f</code></li>
 <li>Database username: <code>pyramid</code></li>
 <li>Host: <code>localhost</code></li>
 <li>Backup file: <code>pyramidDbBackup.tar</code></li>
</ul>
<p>Replace the example values with those used in your environment.</p>
<h3>Windows - Older Bundled PostgreSQL</h3>
<p>For installations still using Pyramid's older bundled PostgreSQL database on port 12130:</p>
<pre class="language-none"><code>"C:\Program Files\Pyramid\postgres\pgsql\bin\pg_dump.exe" -U pyramid -h localhost -p 12130 -F t -f "C:\backup\pyramidDbBackup.tar" pyramid2324f</code></pre>
<h3>Windows - PostgreSQL 18</h3>
<p>For installations that have migrated to PostgreSQL 18, use the PostgreSQL utilities from the separate PostgreSQL installation.</p>
<p>For example:</p>
<pre class="language-none"><code>"C:\Program Files\PostgreSQL\18\bin\pg_dump.exe" -U pyramid -h localhost -p 5432 -F t -f "C:\backup\pyramidDbBackup.tar" pyramid2324f</code></pre>
<p>Ensure that <code>C:\backup</code> exists before running the command.</p>
<h3>Linux - Older Bundled PostgreSQL</h3>
<pre class="language-bash"><code>/opt/pyramid/postgres/pgsql/bin/pg_dump -U pyramid -h localhost -p 12130 -F t -f /home/master/pyramidDbBackup.tar pyramid2324f</code></pre>
<h3>Linux - PostgreSQL 18</h3>
<p>When PostgreSQL 18 has been installed separately, use its pg_dump utility.</p>
<p>If the PostgreSQL 18 utilities are available in the system PATH, an example command is:</p>
<pre class="language-bash"><code>pg_dump -U pyramid -h localhost -p 5432 -F t -f /home/master/pyramidDbBackup.tar pyramid2324f</code></pre>
<p>If multiple PostgreSQL versions are installed, use the full path to the PostgreSQL 18 utility to ensure that the correct version is used.</p>
<p>When prompted for the database password, enter the actual configured password.</p>
<p><strong>Important:</strong> A backup should be stored in a secure location outside the Pyramid installation directory, preferably with a copy on another server or backup storage system.</p>
<h2>3. Restoring the PostgreSQL Database</h2>
<p>The following instructions describe restoring a TAR-format backup using PostgreSQL command-line utilities.</p>
<p><strong>Warning:</strong> Deleting or replacing a database is destructive. Ensure you have a verified backup and have identified the correct target database before proceeding.</p>
<p>Before restoring:</p>
<ol>
 <li>Stop all Pyramid application services that connect to the repository.</li>
 <li>Leave the PostgreSQL database service running.</li>
 <li>Verify that the backup file exists and is valid.</li>
 <li>Confirm the PostgreSQL version, port and database name.</li>
 <li>Ensure the database user has the necessary permissions.</li>
</ol>
<h3>Step 1 - Delete the Existing Database</h3>
<p>If the existing database must be completely replaced, it can be deleted using the <strong>DROP DATABASE</strong> command.</p>
<p>The following commands use the PostgreSQL 13+ syntax with <code>WITH (FORCE)</code>. The older bundled PostgreSQL 9.6 does not support this syntax; active connections must be terminated using a compatible method first.</p>
<h4>Windows - PostgreSQL 18</h4>
<pre class="language-none"><code>"C:\Program Files\PostgreSQL\18\bin\psql.exe" -h localhost -d postgres -U pyramid -p 5432 -c "DROP DATABASE pyramid2324f WITH (FORCE);"</code></pre>
<h4>Linux - PostgreSQL 18</h4>
<pre class="language-bash"><code>psql -h localhost -d postgres -U pyramid -p 5432 -c "DROP DATABASE pyramid2324f WITH (FORCE);"</code></pre>
<p>These examples assume that the PostgreSQL user has permission to drop the database. Otherwise, use an appropriately privileged PostgreSQL account.</p>
<p>For older bundled PostgreSQL versions, use the appropriate older-version procedure to terminate active connections and then run:</p>
<pre class="language-sql"><code>DROP DATABASE pyramid2324f;</code></pre>
<h3>Step 2 - Create the Database</h3>
<p>After deleting the original database, create a new empty database with the same name.</p>
<h4>Windows - PostgreSQL 18</h4>
<pre class="language-none"><code>"C:\Program Files\PostgreSQL\18\bin\psql.exe" -h localhost -d postgres -U pyramid -p 5432 -c "CREATE DATABASE pyramid2324f OWNER pyramid;"</code></pre>
<h4>Linux - PostgreSQL 18</h4>
<pre class="language-bash"><code>psql -h localhost -d postgres -U pyramid -p 5432 -c "CREATE DATABASE pyramid2324f OWNER pyramid;"</code></pre>
<p>For older bundled PostgreSQL installations, use the corresponding psql executable and port 12130.</p>
<p>The commands assume the role <strong>pyramid</strong> already exists. If necessary, use a PostgreSQL administrative account to create the database with the required ownership.</p>
<h3>Step 3 - Restore the Backup</h3>
<p>Use <strong>pg_restore</strong> to restore the contents of the TAR backup into the newly created database.</p>
<h4>Windows - Older Bundled PostgreSQL</h4>
<pre class="language-none"><code>"C:\Program Files\Pyramid\postgres\pgsql\bin\pg_restore.exe" -h localhost -p 12130 -U pyramid -d pyramid2324f -v "C:\backup\pyramidDbBackup.tar"</code></pre>
<h4>Windows - PostgreSQL 18</h4>
<pre class="language-none"><code>"C:\Program Files\PostgreSQL\18\bin\pg_restore.exe" -h localhost -p 5432 -U pyramid -d pyramid2324f -v "C:\backup\pyramidDbBackup.tar"</code></pre>
<h4>Linux - Older Bundled PostgreSQL</h4>
<pre class="language-bash"><code>/opt/pyramid/postgres/pgsql/bin/pg_restore -h localhost -p 12130 -U pyramid -d pyramid2324f -v /home/master/pyramidDbBackup.tar</code></pre>
<h4>Linux - PostgreSQL 18</h4>
<pre class="language-bash"><code>pg_restore -h localhost -p 5432 -U pyramid -d pyramid2324f -v /home/master/pyramidDbBackup.tar</code></pre>
<p>The <strong>-v</strong> option enables verbose output to display restoration progress.</p>
<p>Review the output for errors and verify that the expected database objects and tables have been restored.</p>
<p><strong>Note:</strong> If the backup references PostgreSQL users or object owners that do not exist on the destination server, the relevant roles must be created or appropriate restore options used.</p>
<h2>4. Important Considerations for Pyramid 2025.11 and Later</h2>
<p>Pyramid 2025.11 no longer supports PostgreSQL versions 12 or earlier as its repository database.</p>
<p>Customers who previously installed Pyramid using the <strong>New Internal Repository</strong> option with the older bundled PostgreSQL 9.6 database must complete the PostgreSQL migration before upgrading Pyramid.</p>
<p>The recommended migration guides use PostgreSQL 18. This involves installing PostgreSQL separately, migrating the existing repository database, and changing the repository connection to use the new PostgreSQL instance.</p>
<p>The documented procedure also requires:</p>
<ul>
 <li>Keeping the existing repository database name and credentials.</li>
 <li>Updating the repository port in the Pyramid config.ini file.</li>
 <li>Updating config.ini on additional Pyramid servers in distributed deployments.</li>
 <li>Updating the Local PG data source connection in the Pyramid Admin Hub.</li>
 <li>Verifying that Pyramid works correctly before performing the application upgrade.</li>
</ul>
<p>For installations following the migration guides, the repository port changes from <strong>12130 to 5432</strong>.</p>
<p><strong>Important:</strong> Do not assume that the PostgreSQL installation remains inside the Pyramid installation folder after migration. Use the executables from the separately installed PostgreSQL server.</p>
<p>Follow the complete instructions in the appropriate migration guide:</p>
<ul>
 <li><a href="/t/m1yjmxm/migrating-the-pyramid-database-from-postgresql-9-6-to-postgresql-18-windows" rel="nofollow noopener noreferrer"> PostgreSQL 9.6 to PostgreSQL 18 Migration - Windows </a></li>
 <li><a href="/t/60yjmmq/migrating-the-pyramid-database-from-postgresql-9-6-to-postgresql-18-linux" rel="nofollow noopener noreferrer"> PostgreSQL 9.6 to PostgreSQL 18 Migration - Linux </a></li>
</ul>
<h2>5. Recovering Pyramid After an Upgrade</h2>
<p>If a Pyramid upgrade fails and you need to return to a previous version, ensure that you have a repository backup taken before the upgrade.</p>
<p><strong>Important:</strong> A Pyramid repository cannot be downgraded in place. Recovery requires restoring a compatible backup and following the appropriate application recovery process.</p>
<p>For more information, see:</p>
<p><a href="https://help.pyramidanalytics.com/Content/Root/Guides/installation/Main/Recovery.htm" target="_blank" rel="nofollow noopener noreferrer"> Pyramid Application Recovery </a></p>
<p><a href="/t/m2wwcy/how-to-revert-back-to-a-previous-version-of-pyramid" rel="nofollow noopener noreferrer"> How to Revert Back to a Previous Version of Pyramid </a></p>
<h2>6. Additional Files to Back Up</h2>
<p>Backing up the PostgreSQL repository does not include all files stored on the Pyramid servers.</p>
<p>Depending on the environment, the following folders should also be considered for backup.</p>
<h3>IMDB Data</h3>
<pre class="language-none"><code>C:\Program Files\Pyramid\repository\imdata</code></pre>
<p>Contains data used by Pyramid In-Memory Databases.</p>
<h3>Publications and Rendered Content</h3>
<pre class="language-none"><code>C:\Program Files\Pyramid\repository\general</code></pre>
<p>Contains generated publications and rendered content.</p>
<h3>Uploaded Files</h3>
<pre class="language-none"><code>C:\Program Files\Pyramid\repository\upload</code></pre>
<p>Contains uploaded files used by relevant Pyramid processes.</p>
<p><strong>Note:</strong> These are traditional default Windows locations. The repository data directory may have been configured separately during installation.</p>
<h2>7. Alternative Approach Using DBeaver</h2>
<p>If you prefer using a graphical interface rather than the command line, PostgreSQL backups and restores can also be performed using DBeaver.</p>
<p>See the following article:</p>
<p><a href="/t/h7hk07w/how-to-backup-and-restore-a-postgresql-database-via-dbeaver" rel="nofollow noopener noreferrer"> How to Backup and Restore a PostgreSQL Database via DBeaver </a></p>
<h2>8. Backup Recommendations</h2>
<ul>
 <li>Always take a database backup before upgrading Pyramid.</li>
 <li>Use the actual connection settings from config.ini.</li>
 <li>For PostgreSQL 18, use the separately installed PostgreSQL utilities.</li>
 <li>Ensure that backups are stored outside the Pyramid installation directory.</li>
 <li>Test backups periodically by restoring them in a non-production environment.</li>
 <li>Do not delete a production database unless a verified backup exists.</li>
 <li>Confirm that the PostgreSQL server and client versions are compatible.</li>
</ul>
<p><strong>Note:</strong> The commands in this article are examples. Replace the database name, paths, port, host, and credentials with those used in your own environment.</p>]]></description>
          <pubDate>Thu, 28 Jun 2018 14:41:45 +0000</pubDate>
          <guid>https://community.pyramidanalytics.com/t/1852k1/how-to-backup-and-restore-a-postgresql-database</guid>
          <dc:creator>Daniel</dc:creator>
        </item>

      </channel>
</rss>
