Should I split my tables into different tables when all of the data is dependant on the primary key?
I think we are short on a little bit of information such as what exactly the license is for and how it is to be used. For example, do all products have exactly one license? Can licenses contain multiple products? As the term license is used, I would imagine that each individual would have their own license to use the product (thus one to many relationship). With that scenario, I will assume that a license is only valid for one product and that several licenses can reference a single a product (a one-to-many relationship).

So to satisfy that requirement, we will need two tables. One for the products, and one for the licenses. The product table would contain all product information such as:

Products
-----------
ProductID
Name,
Description,
Price,
(etc)

Licenses
--------
LicenseID,
ProductID,
StartDate,
EndDate,
Amount, -- I believe this is to represent how many individual licenses of this one is used
Limit,  -- And this is to represent how many people can use this current license
(etc)


With this, we have a few benefits. Now, we can license out an individual product to multiple people (again, I am assuming the product is something like software) and we can now change licenses with out affecting the product and if we need to make changes to the product, all the licenses will automatically be updated. A good example of this is the changing of a product description. If products were stored with the licenses, we would have to change all the licenses that used that same product. That's not good and prone to having inconsistent data. 

If I am off base, feel free to let me know. As you can see, I made quite a few assumptions.