Unfortunately, unless you have set something up previously, this is not possible. No default setting captures that level of information, as the log would probably exceed the database size.
also, no-one "logs into" a database. at the time of initial login, you can declare a default database(ie master)
you can capture that, but it's not always useful.
once you have connected when you execute USE OtherDatabase or do query a specific database like select * from MyCompany.dbo.Invoices, that is not captured at all.
so it depends on what you are trying to capture.
if you are trying to capture just plain old usage, like when was the last tiem a table was selected from or updated, you can get some of that information form index stats.
if you want login information for whodunnit information, like what login is doing SELECT, you need an extended event or a trigger to audit that kind of stuff.
If you are trying to capture exactly WHAT rows and columns someone selected, it's a real, real difficult operation. probably impossible.
--help us help you! If you post a question, make sure you include a CREATE TABLE... statement and INSERT INTO... statement into that table to give the volunteers here representative data. with your description of the problem, we can provide a tested, verifiable solution to your question! asking the question the right way gets you a tested answer the fastest way possible!