I will provide an overview of pointers to get you started and refer you to other online tutorials. Then you should ask more specific questions as you encounter problems.
1. Import your data and set a primary key
You already imported your data, but here are more specific steps. If each row has a unique EventID in each of your table, then that would be your primary key (important later), in which case you don't need "enable identity insert" to generate a new one.
Make sure your table is configured so that EventID is set as the primary key in each table, in each table. Instructions here. If there are many rows with the same EventID, things will be more complicated, so I'm assuming they are unique.
2. Define relationships
Define relationships between the 2 tables, by linking them on their primary keys (EventID). Pick a one table as the main one, and the primary key of the second table becomes the foreign key to the first. If there's a 1:1 match between EventIDs, then that's the simplest case to work with.
See tutorial here which shows both the GUI and SQL methods.
3. Use the Query Designer
This is a tool to help you create a SQL query that will join (connect, or link) both tables and show the result. Follow-up tutorial here. Since you have defined the relationships already, the query designer will know how to join them.
In a query, you can pick the columns from each joined tables you want to see, and the query will show them combined as one. You can add filters ("where" criteria) and sorting ("order by") here too.
4. Create a view out of the query you made.
A view is a database term to mean a query that is saved and can be read as if it was a real table, although behind the scenes it's still just the SQL query you created, joining both tables as one. That should answer your second question.
Follow-up tutorial here.
5. Experiment
Once you get familiar with this, you may want to learn SQL more in depth. There's a ton of resources online. And in fact, in SQL steps 2-4 could be replaced by just this:
create view MyBigTableView as
select * from table1
inner join table2
on table1.EventID = table2.EventID
Addendum
If you have more than 1 column as the primary key (the thing that uniquely identifies every single row), that is called a compound or composite key. It's easy to define this type of primary key in the table designer (see stackoverflow answer here), and that will be used to define the relationships, as well as eventually for creating indexes for better query performance (not covered here).
In SQL (whether you have defined the primary key or not) an inner join on 2 tables that have both EventID and SubEventID would look like this:
select * from table1
inner join table2
on table1.EventID = table2.EventID
and table1.SubEventID = table2.SubEventID
