Overview
Control > Settings > Data And Service Usage
The Data And Service Usage screen displays DB data.
It allows you to see how much storage is used and what tables have the most data.
Settings > Data And Service Usage
You can see what is taking up the most database space by going to your control centre and looking at your Data and Service Usage screen.
This shows the top 30 tables by the number of records and size. It also displays the size of your main Affino database.
Note: for some instances, we run custom databases then add the custom DB size to the size above.
It is important for you to regularly check your database size to avoid any surprises, and to maintain the site's responsiveness going ahead, as once it exceeds the agreed service level it will naturally slow down somewhat.
This could in turn lead to the site(s) blipping and longer page load times, which is both bad for the user experience and SEO, and could ultimately result in downtime for your Affino instance.
It means that you will either need to look at clearing out data and downsizing your database(s), or you will need to move up a data service tier.
The two primary ways you can shrink your database are either to delete contacts, or to delete content.
This will also delete all the related stats, conversion events, and other associated data.
As a rule, Affino is optimised and aggregates and removes expired stats in any case to naturally keep your database(s) as small as possible.
Note: you should not reduce the volume of data if the core content, commercial and audience data is valuable to your brand(s).
If you want to clear down some data on your database or move up a service tier, then please let us know.
Note: top tables will vary for different Client.
If there's a table thats missing, please call Support for more details and well provide more details and guidance on how to reduce the data size.
Here is the Name and Description of each table and the data stored within:
Name | Description |
SA_ContentViewUser | Recent user content views, the busier the site(s) the bigger the table. These stats are used on all user records, articles, sections, channels, accounts, site analysis and the analysis dashboard, as well as multiple additional reports. These are kept for a limited time and then used to calculate the aggregate stats. |
NewsletterMessageAppUser | These are the newsletter message users, i.e. anyone a message is sent to. The more messages sent to more individuals the bigger the table. These are kept for a limited time and then used to calculate the aggregate stats. |
AppUser | The core user data table, the more contacts you have in Affino and the more data you have on each one the bigger this table. This is all the critical user data. Note that deleting old and expired contacts, in turn clears out a great deal of analytics data associated with them and is therefore one of the most effective ways to reduce your database size. |
NewsletterMessageRead | The table with the stats on who's read each message. This is kept for a limited time and then use to calculate the aggregate stats. |
SA_ContentViewOther | This is the table which captures all the non user / non bot views and is essential for maintaining consistency with all the scheduled tasks, e.g. to ensure imports and exports run smoothly, that all messages are sent and that security is maintained throughout. These are cleared out relatively quickly once the tasks and security checks are complete. |
NewsletterMessageRecipient | This is a table containing the data on the users who are confirmed recipients of each message. |
MyMessage | These are the personal messages stored in Affino for many message notifications, e.g. ecommerce notifications. They are available through the site in the event that the user did not receive them via email. They are automatically removed after a while. |
ContentViewDay | This is the aggregate data for content views each day across all your sites, and is used for the long term analysis reports, e.g. in the site analysis and analysis dashboard. |
StandardItem | All article content. |
OrderPaymentGatewayHistory | These are all the notifications sent to Affino from the payment gateways, e.g. Stripe regarding each of your transactions. |
SA_ContentViewBot | This is the bot traffic, essential for understanding and enabling / blocking bots. In particular this table is crucial for Affino to automatically identify and regulate any bots which might otherwise overwhelm your site. The data is deleted after a relatively short period to ensure that it does not grow significantly. |
AppUserConversionEvent | These are the conversion events, each of which is recorded and stored uniquely. This can be minimised by putting quantity and time limits on how long they are kept for, and by setting up events to capture 1st, 10th or 100th events and not all individual ones. |
BotBlockLog | This is the log of bots which have been blocked, essential for site security and uptime. |
MediaFileitem | This is the table which contains the identifiers for all the file items which underly your media items. Each image based media item can for example have from between four and eight different images. |
ContentViewConsumeDay | Convent views consumed during the day. These are essential for the analytics and are aggregated daily. |
ContentViewHour | Convent views consumed during each hour of the day. These are essential for the analytics and are aggregated hourly. |
ContentViewMonth | Aggregated content views over the month. These are essential for the analytics. |
ScreenName | The central directory table for all the screen names across your sites in Affino. They cover the screen names for all channels, sections, articles, editions, topics, contacts, accounts and more. |
ContentViewCreatorDay | This is an aggregate views table for the content creators, used for the Dashboard and related analytics. It grows with the number of views and content creators. |
Medialtem | Media file item metadata, note this is not the actual file content. The exception being when the content is pasted in as the metadata, e.g. for searching PDFs / video transcripts. |
DC_SkinDesignStyle | This table contains the design styles. The more styles you have across your site(s) the more data is stored here. It can be reduced by reducing the overall number of styles. |
AppUserTracking | Unique Code generated for each user and stored in that table used for the Tracking Cookie. This grows and declines based on the number of active users / bots / devices. |
MyMessageFolder | Each user has a set of My Message folders for receiving and sending messages. This table contains them and grows with the number of users. |
ContentViewTaxonomyCategoryHour | Content views by Topics each hour. Essential for the Topic analytics. |
BrokenLinkLog | The log of broken links, can be reduced by ensuring that all the key broken links have redirects in place for them. |
ContentViewCreatorHour | This is an aggregate views table for the content creators, used for the Dashboard and related analytics. It grows with the number of views and content creators. |
Order | The order data table. This will grow naturally with more orders. |
AWSSNS | This is the primary system log for email and SMS messages. The data is essential for message debugging and support and there is a cap on how much and how long it is kept. |
EmailLog | This is an additional log for emails not sent via the message campaign. The data is essential for message debugging and support and there is a cap on how much and how long it is kept. |
SA_ContentViewAdmin | This table stores the admin views throughout Affino and is essential for auditing purposes. It can be used to identify what went wrong in the event that an error arises, e.g. someone accidentally deleted or changed critical content, subscriptions or sections. The data is stored on a time limited basis before deletion. |
Meetings:
Google Meet and Zoom
Venue:
Soho House, Soho Works +
Registered Office:
55 Bathurst Mews
London, UK
W2 2SB
© Affino 2024