I need to create a logon trigger where I am able to capture both Windows and SQL Server authentication account users last login time. I am running into the issue of when I log in as a SQL Auth user with public server role permissions only and I get:

I need to create a logon trigger where I am able to capture both Windows and SQL Server authentication account users last login time. I am running into the issue of when I log in as a SQL Auth user with public server role permissions only and I get:

I need to create a logon trigger where I am able to capture both Windows and SQL Server authentication account users last login time. I am running into the issue of when I log in as a SQL Auth user with public server role permissions only and I get:

I am writing a db code, when data is inserted into one table, that related processed data should be immediately inserted into another table with scheduler. I’m thinking using triggers for the same, but as the data is risky and any mistake will be trouble. please suggest should I use triggers or not.

The ask: to capture at bare minimum DELETE queries to a table dbo.DDLEvents; my boss would prefer the entire INSERT and UPDATE as well, but I think that would cause the table to be too massive.

I am trying to do something seemingly simple, but the research I have done on it hasn’t proven helpful.

I like to check in mu update trigger if order_status was set to 90 and it wasn’t before (deleted).

I have a table A and I have defined trigger on it as following: