SQL Server 15.0.4395.2 We have a SSIS package that we run to interface with another system. It is (or was) run from a SQL Server Agent job, and scheduled to run every hour. For reasons outside the scope of this question, the link to the other system became defunct and the package fails whenever it is run. This is not a problem - we disabled the job in SQL Server Agent, and according to the Job Activity Monitor (both the main screen and the job history screen) it hasn't run since 8th August. That's absolutely what we expect to see. But if we go to the database in Integration Service Catalogs and run the All Executions report, that package still shows up as being run (and failing) every hour. There's nothing running with that frequency in SQL Server Agent, where is that job coming from? Is there some other way of scheduling packages to run that won't show up in SQL Agent? It's a fairly old system, so there might be ancient code lurking somewhere!

This may be a daft question as it is coming from a foggy mind. I am trying to determine when the next interval will be of a job that is scheduled to fire on the last day of every x month. In a query, I have calculated ThisMonthsJobTime, ScheduleStartJobTime and I am trying to determine the case on how to know when, at any given point in time, when is the NextFiringTime. Let's say I have a SQL Server job starting at 02/05/2025 10:30:00 PM and it has been configured to run on the last day of the month at 10:30:00 PM every 2 months. The @freq_recurrence_factor = 2 I am reading this as it will fire on 2/28, skip 3/31 and 4/30, and fire again on 5/31 and so on. Can I get a confirmation on this as the documentation does not go into detail about that? To the query question. Is there any date time math magic that can be used to determine the next job run time at any given point in time? I have been working some stuff. SELECT IntervvalOfX, ScheduleBeginDate, DATEADD(DAY,DATEDIFF(DAY,ScheduleBeginDate, EOMONTH(scheduleBeginDate)),ScheduleBeginDate) AS ScheduleStartJobTime, NextStartJobTime = 'some math based on start-time, getdate() and IntervalOfX?' FROM MyScheduleTable

I'm trying to install pgAgent on my device. During the installation using the stackbuilder, the last step requires me to add the operating system username and password as below: However, after entering the password of my postgres superuser account, i'm shown the below dialog box: Every resource available online mentions that the username and password should be the superuser's. I've tried using the Windows account details as well as creating a new user within postgres and using its details. Any help would be greatly appreciated. I'm using PostgreQL v13, and pgAgent v4.2.1

I've decided that I no longer want to use SQL Server Agent Jobs. They're tightly coupled to SQL Server, cause interesting security/permissions problems, and can be complicated to sequence. I instead want to replace them with AWS services, under the assumption that they will be easier to move to Postgres should I ever switch away from SQL Server. I currently use SQL Server Agent Jobs for the following tasks. Can they be done with AWS Services? - Running T-SQL code at regular intervals without any care for what it returns, e.g. updating a particular table once an hour. - Running T-SQL code at regular intervals and using its results to update CloudWatch metrics. - Running T-SQL code at regular intervals, exporting the result to CSV, then saving that CSV in an S3 bucket. - Running SQL Server Maintenance Plans. - Firing SSIS packages.

Looking for a way to implement this STIG. What method should I use to monitor SQL Server, when it is shutdown due to "Shutdown on Audit Failure"? SQL Server must provide an immediate real-time alert to appropriate support staff of all audit failure events requiring real-time alerts. I have found Event ID: **33219** Parameters: - Cannot store a password, so difficult to use "Windows Scheduled Task" - On a domain, remember not able to store a password - PowerShell script:

$recipients = ","
 Send-MailMessage -To $recipients -Subject "SQL Audit Failure" -Body "SQL has shutdown due to Audit Failure." -SmtpServer NameOrIPAddress -From SQLEmail@domain.tld -Priority High

PostgreSQL 14 - Windows Server 2012 ----- I have a scheduled task every day at 5 AM. It executes an sql file with an update query and some refresh materialized views. - According to Windows Server, the task is executed without any error. - In the log file, I can't see any line about the queries written in the sql file. - The views that are supposed to be refreshed are not. - If I execute all the queries contained in the sql file by hand one by one, it works. - The user executing the task is the same executing all others successfully scheduled tasks, so same password (and no pwd issue in Windows log). Why is it that, despite the apparent success of the task, the requests don't run?

I was reading postgresql replications solution but, even I just starting understaning how it works, another doubt has arrisen. I'll be using postgres internal replication solution but as far as I understand, every event will be replicated just as it is achieved; for example, if I insert some data into the master, automatically it will be replicated to the slave...Am I right? Well, is that so, I was searching for way of scheduling this replications as a passive backup but the thing is, I need for example, every monday on the night the database gets replicated with all the data it had inserted in it that day to a slave database in Amazon EC2 virtual servers. I was thinking on using cron as a first approach but reading postgres documentation I got aware that practically only configuring the necessary files, postgres do it for you... So, how could I schedule replication in just desired moments? PD.-The schedule may vary so it needs to be completely generic, also...I'm using Ubuntu 12.04 and PostgreSQL 9.1 as in the master as in the slave. Thanks

Using the BigQuery C# API, I can retrieve a list of job IDs : BigQueryClient _client = BigQueryClient.Create(...); ... foreach (var page in _client.ListJobs(projectId).AsRawResponses()) if (page.Jobs != null) // This does happen occasionally foreach (var job in page.Jobs) yield return job.Id; This seems to give me all jobs ever run (or at least within some significant time horizon; it's tens of thousands of records). Still, I'd like to get the details for some jobs and see if I'm at least on the right track. I can retrieve a BigQueryJob object using BigQueryClient.GetJob() (there's no C# doc, but the Java sample code is similar ), but the information returned is very limited: current state, any errors encountered, some basic statistics, etc. There's nothing about schedules. Is there a separate command to retrieve details on scheduled queries? I can't find any such methods in the client.

We have installed **pg_cron** extension on PostgreSQL 13 database. postgresql.conf file:

shared_preload_libraries = 'pg_cron'
cron.database_name = 'pg_cron_db_name'

Also we enabled trust authentication for connections coming from localhost in pg_hba.conf:

#IPv4 local connections:
host   db_name    postgres,pg_cron_user    127.0.0.1/32         trust
host   all        all                      0.0.0.0/0            md5

We have run this query from postgres user to schedule a simple job for a database db_name (other than the one **pg_cron** was installed in):

-sql
SELECT cron.schedule_in_database('job1', '5,10,20,30 17 * * *', $$SELECT 1$$, 'db_name');

Everythings works fine on our staging database. \ But on our production DB the job is never executed. Table cron.job_run_details is empty and there are no entries in a logfile (even error ones).\ Versions of production and staging DBs are the same. We performed identical steps to set up **pg_cron**. The only difference we can think of is that staging DB is running on on-premise server while production DB is running on Azure's virtual machine. We tried to switch to unix domain socket to allow connections from localhost by running:

-sql
UPDATE cron.job SET nodename = '' WHERE jobid = ;

This helped, but temporarily. Job has been successfully executed three times and after that stopped to run again. Any ideas on how to solve this problem are appreciated.

Can you please help me how to execute a stored procedure automatically in SQL database without any transaction in SQL? I want to execute on particular fix time.

We have some batch scripts as task scheduler jobs, which are running good from few years. These jobs connects to DB and will do multiple inserts and update operations using sqlplus, sqlldr and java code (jar files). Suddenly we observed a very big performance issue across all these jobs. After monitoring some scripts for a long time, we identified that these jobs are waiting randomly from time to time and then continue running. There is no particular time frame for how long they wait or at which phase query execution they wait. Its completely random. A web Application is deployed in same machine, connects to same database. This application performance is also dropped from the same day. This is severely hindering business activities. I really appreciate any advise\suggestions that can help us resolve this issue. Oracle DB: 18c We tried below activities. 1. Validated windows app server and didn't found any new installations\updates\patches. 2. Coordinated with network team and found no traffic issues are identified on both app and DB servers. 3. No heavy load packets are on DB DNS 4. DB is running normal. It is a shared instance and no other application\team found any issues in performance. Some how i feels like some other process is holding our web application and task schedule connection processes. I am banging my brains to bring this connection performance to normal situation. Any advise is highly appreciated.

This job already has one schedule that runs on the first of the month. However, we need to run the job on a different schedule if the first of the month falls on a Sunday. It appears to me that the SQL Server Agent Job Properties Scheduler GUI is not flexible enough to handle this type of schedule. I am continuing to research this items. Any thoughts or examples (if powershell is needed) would be appreciated. We are running SQL Server 2019 on Windows Server 2019. To clarify, the job runs on the first of the month starting at 5 A.M. If the first of the month falls on a Sunday, we need the job to start at 6:15 A.M. So, maybe I can use something like: case datepart(dw,getdate()) = 1 then 'execute one job schedule' else 'execute another job schedule' end.

I have deployed my SSIS package using the project deployment model to the SSIS catalog and experience a strange validation error when I try to execute the package. I believe this is due to a privileges issue or I may have configured our data import process wrong. Let me give you an overview on the process: - Windows Task Scheduler is being used - Scheduled Task executes a long-running file download process (using Powershell) - Scheduled Task triggers execution of the SSIS package (using Powershell and SMO) - Scheduled Task is configured to run as a domain account (see privileges below) Note: all these steps, including account creation, are automated using guidance from [here](http://blogs.lessthandot.com/index.php/datamgmt/dbadmin/mssqlserveradmin/ssis-deployment-with-powershell-adding/) . Scheduled Task Account Privileges: - Windows: Users Group - SQL Catalog: Read on Catalog Folder, Read on Environment, Read and Execute on Project - Destination Data Database: db_datareader, db_datawriter - Source Data Database: db_datareader, db_datawriter Steps To Reproduce The Error: - Right-click scheduled task, choose 'Run' - Package execution is *triggered* successfully - Open SSMS, view Execution logs. Package execution immediately failed with a validation error "Cannot create task from XML for task "[taskname]", type "SSIS.ReplacementTask" due to error 0x80070057 "The parameter is incorrect." While diagnosing this issue, I wanted to rule out privileges and ensure the account could see the SSIS project in the catalog, so I executed SQL Server Management Studio as my Scheduled Task account. The Package validated and ran to completion successfully. Here's the bit that is very confusing.! After performing the above step (login to SSMS as Task Scheduler account), I could successfully trigger, validate and execute the scheduled task from the Task Scheduler! I am now able to reliably replicate these steps: 1. Execution Fails 2. Login to SSMS As Task Scheduler Account 3. Execution Succeeds *Theory: the 'first time configuration' that occurs when launching SSMS as the Task Scheduler account is configuring user specific registry keys. I have confirmed that when I do not log in as my custom account, when the package tried to execute it complains that user specific registry keys are not found via Process Monitor.* My Questions: - Should we be using the Task Scheduler instead of SQL Server Agent? I orignally chose Task Scheduler because the powershell download task was long running and needs access to network shares - Can I trigger a package to execute from a Scheduled Task, but have it execute as a different account? Thanks for any help you can offer - I'm quite confused!

Can we sync a mongodb database to another incrementally based on a schedule? Say, once every night at 12 am? **Background:** We have a MongoDB replica cluster consisting of 3 instances, all located within one data center. For backup, the company is acquiring another server in a different country. This rises two questions for us. 1. Does MongoDb allow us to do schedule syncing. 2. Can the syncing be incremental by not replacing data that is already synced. We initially thought of adding the new server to the replica set as a passive replica. However, we got input that it will slow down the cluster as the new server will have high latency.

I am trying to run a pg_dump through a scheduled task in windows. I have two batch files. One creates the task. The other one runs the pg_dump. Even though the pg_dump works with the current user with no problem, I have to run the pg_dump as a System because I want it to run even if the user is not logged on. Unfortunately, to run a task when a user is logged off, you have to run it in System user and that doesn't work for pg_dump. I couldn't see any error. It simply creates an empty backup file and after that, pg_dump keeps on running, blocking future runs. Part of my pg_dump code is the following. %PG_BIN%pg_dump -h %PG_HOST% -p %PG_PORT% -U %PG_USER% -F c -b -v -f %BACKUP_FILE% %DB% Part of my Schtaks code that creates the task. SchTasks /Create /SC MINUTE /mo 30 /RU "SYSTEM" /TN "Database Backup" /TR "%SCRIPT_DIR%backup_db.bat"

I have upgraded a database to SQL 2017. A SQL Agent Job that previously ran now fails with this error: Unable to start execution of step 1 (reason: JobOwner DOMAIN\USERNAME doesn't have permissions to use proxy 4 for subsystem PowerShell). The step failed. This job ran before the upgrade, so I'm confused why permissions would have changed. But no matter, I grant permissions with this script: USE msdb GO EXEC dbo.sp_grant_login_to_proxy @login_name = N'DOMAIN\USERNAME', @proxy_id = 6 GO Which then reminds me that the user in question is an admin, and can be neither granted nor denied anything: 'DOMAIN\USERNAME' is a member of sysadmin server role and cannot be granted to or revoked from the proxy. Members of sysadmin server role are allowed to use any proxy. So what am I missing? How can I fix this, or where should I look to determine what the underlying problem is?

I'm working on an SQL server database, containing orders and machines, executing those orders. Not more than one active order can be assigned to a machine at the same time. In other words: this SQL request can never yield a result: SELECT MachineId FROM Orders WHERE (Orders.Status=1) GROUP BY MachineId HAVING COUNT(Id)>1 I have this SQL request open in a Microsoft SQL Server Management Studio environment, and every time I press F5, I indeed see no results. However, I am sure that there have been times where that SQL query did yield results, and I'm interested in those times and the results of that query at those times. Does anybody have an idea on how I can find this out? (The "archive-log" tag is just an idea) Thanks in advance

I'm having the problem, while insering a row using rpc through the nodejs library, with user **service_role**. i gave permission to all roles. Without exception. And for **service_role** I even gave it all privileges in the whole database just for the sake of testing. launching the cron from the dashboard editor. And after giving the permission to **postgres** as above. And as per this thread
It worked. The cron worked just right. But then when i do it through **service_role**. From nodejs rpc insert. Which trigger a trigger procedure. Which run all right. I made a command to ccheck which insert in a log table I created. In mean time, the job is added to the jobs table. And being active. However no command run. (the mentioned user I gave him the privileges for cron. But then after I gave him even access to all. Nothing works.) Any ideas or pointing. Here my trigger function The schedule command is temporal I took from the one that worked on the dashboard to make sure ..? How can this be explained ? Any ideas or points ? Anything may be special about supabase ? May be the **service_role** user have some restriction ??? or . i'm just out of clues hhh ( an official ref: https://supabase.io/blog/2021/03/05/postgres-as-a-cron-server )

I would like to call a stored procedure on a regular basis. On Oracle, I would create a job for this. I have found that Postgresql can mimic this well by using an external tool (cron etc) and PgAgent. Do you know of an "internal" alternative which wouldn't involve the external tool ? - I want to avoid security concerns with the password stored on the command line of the pgAgent. - I want to avoid any additional system configuration for hiding the password (~/.pgpass). **Postgresql 8.3**
**Linux RedHat 64bit**

This schedular i made doesn't work how i would like it to work. The idea is that it will run every day in a time periode from 06:15:00 till 23:59:59 and in that only periode run every hour That means it will run on 06:15 - 07:15 - 08:15 etc.. till 23:15 and start over again the next day Server version: innodb_version:5.7.25 DELIMITER | /* 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 */ ALTER EVENT Database.Import_data01_view ON SCHEDULE EVERY 1 HOUR STARTS '2019-04-15 06:15:00' ON COMPLETION PRESERVE ENABLE DO BEGIN /* do things */ END | DELIMITER ; With the info i found my own solution for it: DELIMITER | /* 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 */ ALTER EVENT Database.Import_data01_view ON SCHEDULE EVERY 1 HOUR STARTS str_to_date( date_format(now(), '%Y%m%d 0615'), '%Y%m%d %H%i' ) ON COMPLETION PRESERVE ENABLE DO BEGIN IF time(CURRENT_TIMESTAMP) between time('06:14:59') and time('23:59:59') THEN /* doe something */ end if; END | DELIMITER ;