New answers tagged

0

Since you recently upgraded a few months ago from SQL Server 2005 EE to 2012 SE, you should save off and clear your event logs because SqlAgent may crash when it sees Event Log IDs from an older build of SQL Server. For example, the Agent may crash because it reads an event logged by a SQL Server build earlier than the current build, which only contains data ...


0

As stated in the Note of MSDN Create and Attach Schedules to Jobs Only one instance of the job can be run at a time. If you try to run a job manually while it is running as scheduled, SQL Server Agent refuses the request. Then I'd rather rewrite the SSIS package to do the paralelism inside the package. As I don't use SSIS - except with ...


0

Only a member of the sysadmin group can execute SQL Agent jobs. The only way around this is create a set of credentials having administrative access of the server side and creating a proxy account, using those credentials. Then the proxy account can be used to run the SQL Agent job.


0

Rather than doing this on a per job basis (checking every job for the state of the server before deciding to continue), I've created a job running on both servers to check to see what state the server is in. If its primary, then enable any job that has a step targeting a database in the AG. If the server is secondary, disable any job targeting a ...



Top 50 recent answers are included