What is shown in a notification email is what is available from AF attributes. There are no attributes that can hold a table, there is no way to do this.
If you knew that each request would only result in a few results (say a small table with 2-3 rows and 2-3 columns), you could create a Data Reference for each entry in that table and make reference to those in your email.
An other way, is if you had your database content that is accessible from a web, and different views of this database could be accessible via different URLs, you could create URI Builder data reference to access your different views. Your email would then include links to your external database.
An other possibility, as your data is not large, you may try to include all of it in an Excel sheet and email that sheet as an attachment in notifications.
The users that receive the excel sheet would then need to know how to filter down the data in that excel sheet to view the relevant data. It is possible to use SQL queries on Excel sheets, so it may be possible to simply shift a slight modification of your query in your notification email.
Not impossible, just tricky, involving many components. Also this is not a common way to achieve things like these. I would use Notifications to send short bits of information. More elaborate datasets are better left to interfaces, reporting, etc.
One approach here: Generating a Daily Report of "Bad" Values using FilteredSummaries