.png?version=1&modificationDate=1662627367996&cacheVersion=1&api=v2&width=226&height=72)
Have a tip of your own to share? Drop us an email and we will be sure to reward you with some SWAG ;-)
Eleven years day in, day out with this application and you learn a thing or two. We polled our team and asked them for their top 5 pro moves when using SQL for Confluence and here's what they said:
1. Start with valid SQL
Where possible, test your SQL using a native database client. This allows you to validate and optimize your query prior to it being used within a SQL macro.
2. Copy + Paste
When using SQL macros on a page, it's often easier to copy and paste an existing SQL macro and use it as a template. This will save time and ensure the configuration works.
3. Cache for better performance
If your Confluence pages have many visitors, you can drastically improve performance by caching your SQL macro to reduce costly database round trips.
4. Use application server based data source profiles
For larger environments, we strongly encourage that you configure our app to leverage application server based data source profiles. Although there is slightly more upfront configuration work, the performance improvements can be quite significant.
5. The future is bright
Our favorite pro tip is to leverage the Future Macro on busy Confluence pages with one or more SQL macros or external calls being made. This macro allows your Confluence users to see some content rendered right away while the server works its magic to present the remainder of the page in its entirety.
