From: daryl on 5 May 2010 20:47 I have a customer that is having issues with SQL jobs being duplicated. The SQL jobs include db backups and data imports. The result of this issue is that there would be duplicate backup (.bak) files and multiple data imports. This fill up disk space fast and the data imports are corrupted. If I stop SQL Agent or the SQL jobs, those SQL backups and imports still run, but it does only one instance! However, it's a mystery of how it's being processed since the SQL agent and jobs are disabled. This issue just started to occur over the past two weeks. We tried rebooting the server and the SQL services, but no success. There are no scheduled tasks anywhere. Customer is on SQL 2005 on Windows 2003. This is a stand alone server. There is no replication and no clusters. Any ideas or suggestions?
From: Sylvain Lafontaine on 5 May 2010 20:53 Did you check the Window's scheduler too? -- Sylvain Lafontaine, ing. MVP - Windows Live Platform Blog/web site: http://coding-paparazzi.sylvainlafontaine.com Independent consultant and remote programming for Access and SQL-Server (French) "daryl" <daryl(a)discussions.microsoft.com> wrote in message news:7C78B2FC-8AA4-4CAB-805E-783310ACEFED(a)microsoft.com... >I have a customer that is having issues with SQL jobs being duplicated. The > SQL jobs include db backups and data imports. The result of this issue is > that there would be duplicate backup (.bak) files and multiple data > imports. > This fill up disk space fast and the data imports are corrupted. > > If I stop SQL Agent or the SQL jobs, those SQL backups and imports still > run, but it does only one instance! However, it's a mystery of how it's > being > processed since the SQL agent and jobs are disabled. > > This issue just started to occur over the past two weeks. > We tried rebooting the server and the SQL services, but no success. > There are no scheduled tasks anywhere. > Customer is on SQL 2005 on Windows 2003. > This is a stand alone server. > There is no replication and no clusters. > > Any ideas or suggestions? >
|
Pages: 1 Prev: Performance Benchmark for SQL 2000 & 2005 Next: MS ACCESS & SQL 2005 Security |