You'd need a login system - IP addresses don't uniquely identify a user.
As far as internet IP addresses go, they are "shared" by all users who connect through the same router for example - so everyone in a company is likely to have the same IP address. And unless the user (or his company) has selected and paid extra for a static IP address then even that is "shared" - each time the router is power cycled you may or may not be using the same IP address afterward.
For LAN IP addresses, it's even worse as they are commonly pooled, and allocated on a "first come, first served" based when a device connects to the router / hub.
So relying on IP addresses to uniquely identify users is a poor idea - it's far, far too easy to get the wrong person!
What you need is a good solid user login system, combined with software in your app and / or your DB to record user accesses in a separate table: the user, a timestamp, and what they accessed goes into a audit log table. If you combine this with individual logins for SQL (which restrict what the user can do to only what they are allowed, SQL can maintain these audit logs for you:
SQL Server Audit (Database Engine) - SQL Server | Microsoft Docs[
^]
Don't expect this to be a ten minute job: anything to do with security needs very careful planning in advance, or you can trip yourself up far, far to easily, and either leave yourself vulnerable, or find yourself locked out of your own system.
Submit an article or tip