@Nafila Afrin Thanks for reaching out and apologies for delay on this.
1) Yes the logs do show up with same Event ID in most case, 33205, this is by design as All SQL audit events are generated with Event ID 33205
2) You can surely filter out the data with what you need on basis of actions something like this :
SQLEvent
| where LogonResult has "failed"
| summarize count() by CurrentUser, Reason
Check this for more customized KQL queries to understand how you can generate different insights :
https://techcommunity.microsoft.com/t5/azure-sentinel/monitoring-sql-server-with-azure-sentinel/ba-p/1502960
If you have a specific requirement which is not mentioned on that do let us know.
Please remember to "Accept Answer" if any answer/reply helped, so that others in the community facing similar issues can easily find the solution.