| Tip |
|---|
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 so you can validate the syntax and optimize the query before embedding it within a SQL Macro.
2. Copy + Paste
If you are planning to include more than one SQL statement on a page, then it's often easier to copy+paste an existing SQL Macro and use it as a template. This will save you time and ensure that your configurations are in proper order. You can do this by editing the Confluence page and highlighting the Macro body.
3. Cache for better performance
If your Confluence pages have many visitors, you can drastically improve performance by caching your SQL Macro, thus reducing costly database round trips.
4. Use Application Data Source Profiles
For larger environments, we strongly encourage that you configure our app to leverage Application Data Source Profiles. Although there is slightly more upfront configuration work, the performance improvements can be quite significant.
5. The Future is bright
Of all the Pro Moves we observe in the wild, we love when our customers leverage the Future Macro on busy Confluence pages with one or more SQL Macro or external call being made. This provides your Confluence users with a pleasant experience while the server works its magic to present the page in its entirety.
| Include Page | ||||
|---|---|---|---|---|
|