rajborntodare is correct;
the information is not saved anywhere on SQL server, unless you explicitly added one of the many audit options available to SQL server.
so going forward, I would recommend adding an extended event to start capturing the specifics, or maybe a server side trace
a trace is probably easier to set up, as extended events , even for me, are a little more difficult without a copy/paste example.
the extended events have two distinct advantages though: As I understand an explanation form Grant Fitchey,
a trace captures data, THEN applies any filters you may have added;
extended_events apply the filter FIRST,then captures the data, resulting in a lower impact on the server.
The second thing is a trace is stopped whenever the SQL service stops; you have to recreate the trace(usually by calling a procedure at startup) to recreate the trace.
extended events use the service broker, and don't get stopped automatically like that.
there are other options like enabling the built in C2 Level auditing (which is really a server side trace), SQL Audit, SQL Trace, and SQL Change Data Capture, but some of those items require the enterprise versions.
--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!