New answers tagged

1

Try this: BEGIN DBMS_SCHEDULER.CREATE_JOB( job_name => 'delete_old_rows', job_type => 'PLSQL_BLOCK', job_action => 'delete_trips;', start_date => SYSTIMESTAMP, repeat_interval => 'FREQ=SECONDLY', end_date => add_months(sysdate,12), auto_drop =&...


0

I have experienced this behavior before, where the AGs "blip:" from PRIMARY to RESOLVING and back to PRIMARY from SECONDARY to SECONDARY It's my understanding that, on a system with a small number of logical processors (1-4), and with multiple AGs (or AGs with many databases), some of these "blips" are unavoidable. Especially if the server is a VM with ...


4

When you do that in a job it basically ends the session and rolls back the transaction when the job finishes. You can trace that using SQLTransaction event class in Profiler. That's the reason why you do not see any open transaction/sessions or the work being done.


3

uxcolebsrep$ is probably the SQL Server name itself. In this case, as you are using a linked server, that makes sense. Your actual Agent service account is a local account to your sql server. It does not exist on the remote Linked Server so SQL uses the Machine account to try to connect to the remote SQL Server (the one in the linked server). To get ...


Top 50 recent answers are included