SQL Job Owners

Good morning,
At present, if a user creates a SQL job, the owner of that job is usually the user. I think this is the case because the users are NOT sysadmins. However, we are wondering of the implications of scheduling a second job to alter all jobs to being
owned by the SQL Server Agent account. This job would run each night.
I know that it might affect users being able to alter the jobs they have created, but that isn't a problem in our environment as, ideally the DBA's would be handling all of this, or the users would be using their admin accounts (which DO have sysadmin permissions
and therefore the owner is sa (as far as i remember)).
Are there any other potential gotchas which anyone can think of?
Regards,
Andy

In addition:
One obvious consequence if changing job owner is that you now won't see who created the job in the first place. I.e., the owner can serve as a type of "documentation". This is easy to fix since we can specify comments for a job, and minimum comment
level, IMO, is who is responsible for the job and what databases is affects.
If you handle above, then I don't see any issues changing job owner by those that already are sysadmins to "sa". That will not change the security picture at all.
But changing owner for jobs current owned by non-sysadmins, I do not recommend. My first though here is to ask you "Why do you want to do that?". It changes the permission situation (see the links) and somebody knowing that you do this un-attended
can create a job that this person himself isn't allowed to do, and next morning this job is suddenly executed (being owned) by a sysadmin/Agent service account. Really really scary!
Tibor Karaszi, SQL Server MVP |
web | blog

Similar Messages

Sql Agent Job Failed after changing job name to sa Error(The job owner does not have access )

I changed job owner to sa and it worked well, But now it fails saying job owner does not have sever access and shows job owner as previous owner Name even after it changed to sa?
Help......

EXEC msdb.dbo.sp_update_job @job_id=N'7d4d4040-b79c-4022-9d19-e449497ab60e',
@owner_login_name=N'sa'
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Consulting:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance
SQL Server Integration Services:
Business Intelligence

Running a SSIS package with SQL Job and Linked Server

I have a SSIS 2008 package. In one of the Script task I am calling a stored procedure which is using Openquery using linked server. I deployed this package with protection level as "EncryptWithPassword" and gave a password to the package.
Created a SQL job and edited its command line to include the password. If I login to SQL Server Mgmt Studio with Windows Authentication and run the job manually it runs fine. But when I schedule it then I get an error that "The Communication link to Linked
server failed".
Please help

Hi Vivek.B,
The issue should occur because the SQL Server Agent Service Account or SQL Agent Proxy account under which the job step runs doesn’t have sufficient permissions on the linked server.
If the job owner is the sysadmin fixed server role, the job can be run under the SQL Server Agent Service Account or a proxy account, then please make sure the SQL Agent Service Account or the proxy account has corresponding login on the linked server. If
the job owner is not a sysadmin fixed server role, the job must run under a proxy account. In this case, make sure the proxy account has a corresponding login on the linked server.
Reference:
http://blogs.msdn.com/b/dataaccesstechnologies/archive/2009/10/13/who-owns-my-job-and-who-runs-it.aspx
Regards,
Mike Yin
TechNet Community Support

SSIS importing comma delimited with double quote text qualifier - Works in VS - SQL Job ignores text qualifier and fails (truncation)

I've created an SSIS package to import a comma delimited file (csv) with double quotes for a text qualifier ("). Some of the fields contain the delimiter inside the qualified text. An example row is:
15,"Doe, John",IS2,Alabama
In SSIS I've specified the text qualifier as ". The sample output in the connection manager looks great. The package runs perfectly from VS and when manually executed on the SSIS server itself. The problem comes when I schedule the package to run via SQL
job. At this point the package ignores the text qualifier, and in doing so pushes half of a field into the next available column. But instead of having too many columns, it concatenates the last 2 columns ignoring the delimiter. For example (pipes are fields):
15|"Doe| John"|IS2,Alabama
So the failure happens when the last half of a field is too large to fit into the next available field. In the case above _John" is 6 characters where the IS2 field is char(3). This would cause a truncation failure, which is the error I receive from the
job history.
To further test this I created a failure flow in my data flow to capture the records failing to be pulled from the source csv. Out of ~5000 records, ~1200 are failing, and every one of the failures has a comma delimiter inside the quoted text with a 'split'
length greater than the next ordinal field. The ones without the comma were inserted as normal and records where the split fit into the next ordinal column where also imported, with the last field being concatenated w/delimiter. Example records when selected
from table:
25|"Allan Percone Trucking"|GI6|California --Imported as intended
36|"Renolds| J."|UI6,Colorado --Field position offset by 1 to right - Last field overloaded
To further ensure this is the problem, I changed the csv file and flat file connection manager to pipe delimited, and sure enough every record makes it in perfectly from the SQL job execution.
I've tried comma delimited on the following set ups. Each set up failed.
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 80
SSIS Server 2008 R2 RTM
DB Server 2008 RTM
DB Compat 100
SSIS Server 2008 R2 RTM
DB Server 2008 R2 RTM
DB Compat 100
Since a lot of our data comes in via comma delimited flat files, I really need a fix for this. If not I'll have to rebuild all my files when I import them to use pipe delimiters instaed of commas. I'd like to avoid the extra processing overhead if possible.
Also, is this a known bug? If so can someone point me to the posting of said bug?
Edit: I can't ask the vendor to change the format to pipe delimited because it comes from a federal government site.

Just wanted to share my experience of this for anyone else since I wasted a morning on it today.
I encountered the same problem where I could run the package fine on my machine but when I deployed to a server and ran the package via dtexec, the " delimeter was being replaced with _x0022_ and columns all slurped up together and overflowing columns/truncating
data etc.
Since I didn't want to manually hack the DTS XML and can't install updates, the solution I used was to set an expression on the textdelimiter field of the flat file connection with the value "\"" (a double quote). That way, even if the one stored in XML
gets bodged somewhere along the way, it is overridden with the correct value at run time. The package works fine everywhere now.

Execute Process Task showing all the SSIS Config variables in SQL Job History

Hi,
Am using an Execute Process task to execute my child package. And executing the Parent package from a SQL JOB.
I am using the same config file for both Parent and Child packages.
After the Job execution was Successful / Failure, in Job history it is showing all the variables from Config file which are not using in Child package. With the below message.
"The package path referenced an object that cannot be found"
I don't want to catch all the Variables information in Job History. Instead I need only the Success / Failure message.
PFA Screen.
Thanks,
Sailaja

see
http://www.mssqltips.com/sqlservertip/1417/custom-logging-in-sql-server-integration-services-ssis/
https://www.simple-talk.com/sql/ssis/ssis-event-handlers-basics/
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Run Multiple SSIS Packages in parallel using SQL job

Hi ,
We have a File Watcher process to determine the load of some files in a particular location. If files are arrived then another package has to be kick-started.
There are around 10 such File Watcher Processes to look for 10 different categories of files. All 10 File Watcher have to be started at the same time.
Now these can be automated by creating 10 different SQL jobs which is a safer option. But if a different category file arrives then another job has to be created. Somehow I feel this is not the right approach.
Another option is to create one more package and execute all the 10 file watcher packages as 10 different execute packages in parallel.
But incase if they don’t execute in parallel, i.e., if any of the package waits for some resources, then it does not satisfy our functional requirement . I have to be 100% sure that all 10 are getting executed in parallel.
NOTE: There are 8 logical processors in this server.
(SELECT cpu_count FROM sys.dm_os_sys_info
i.e., 10 tasks can run in parallel, but somehow I got a doubt that only 2 are running exactly in parallel and other tasks are waiting. So I just don’t want to try this option.
Can someone please help me in giving the better way to automate these 10 file watcher process in a single job.
Thanks in advance,
Raksha
Raksha

Hi Jim,
For Each File Type there are separate packages which needs to be run.
For example package-A, processes FileType-A and package-B processes FileType-B. All these are independent processes which run in parrallel as of now.
The current requirement is to have File Watcher process for each of these packages. So now FileWatcher-A polls for FileType-A and if any of the filetype-A is found it will kick start package-A. In the same way there is FileWatcher-B, which looks for FileType-B
and starts Package-B when any of FileType-B is found. There are 10 such File Watcher processes.
These File Watcher Processes are independent and needs to start daily at 7 AM and run for 3 hrs.
Please let me know if is possible to run multiple packages in parallel using SQL job.
NOTE: Some how I find it as a risk, to run these packages in parallel using execute package task and call that master package in job. I feel only 2 packages are running in parallel and other packages are waiting for resources.
Thanks,
Raksha
Raksha

SSIS Package compiled successful, in SQL Server Integration Service package executed sucessful, But fail to run in MS SQL Job Scheduler

Hi Everyone,
I having a problem to transfer data from MS SQL 2005 to IBMAS400. Previously my SSIS was running perfectly but there is some changes I need to be done in order for the system to work well. Considers my changes are minimal & just for upgrades (but I did
include DELETE statements to truncate AS400 table before I insert fresh data from MS SQL table to the same AS400 table), so I compile my SSIS package & it run successfully & I passed it into MS SQL Integrated Service as 1 of the packages & manually
executed the package & the result is the same, that mean it was successful again but when I try to run it in a MS SQL Job Scheduler, the job failed with these message shown below as extracted from the job View history.
Date today
Log Job History (MSSQLToAS400)
Step ID 1
Server MSSQLServer
Job Name MSSQLToAS400
Step Name pumptoAS400
Duration 00:00:36
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
Executed as user: MSSQLServer\SYSTEM. ... 9.00.4035.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved.
Started: today time
Error: on today time
Code: 0xC0202009 Source: SSISMSSQLToAS400 Connection manager "SourceToDestinationOLEDB"
Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred.
Error code: 0x80004005. An OLE DB record is available.
Source: "IBMDA400 Session"
Hresult: 0x80004005
Description: "CWBSY0002 - Password for user AS400ADMIN on system AS400SYSTEM is not correct ". End Error
Error: today
Code: 0xC020801C
Source: Data Flow Task OLE DB Destination [5160]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationClearData" failed with error code 0xC0202009. There may be error messages posted before
this with more information on why the AcquireConnection method ca... The package execution fa... The step failed.
So I hope somebody can shed some hints or tips for me to overcome time problem of mine. Thanks for your help in advance. As I had scoured thoroughout MSDN forums & found none solution for my problem yet.
PS: In the SQL Integrated Services when I deployed the package I set the security of the packages to Rely on server...
Hope this will help.

Hi Ironmaidenroxz,
From the message “Executed as user: MSSQLServer\SYSTEM”, we can see that the SQL Server Agent job ran under the Local System account. However, a Local System account doesn’t have the network rights natively, therefore, the job failed to communicate with
the remote IBMAS400 server.
To address this issue, you need to create a proxy account for SQL Server Agent to run the job. When creating the credentials for the proxy account, you can use the Windows domain account under which you executed the package manually.
References:
How to: Create a Credential
How to: Create a Proxy
Regards,
Mike Yin
TechNet Community Support

Send error messages in DatabaseMail when SQL Job fails/succeeds

Hi ,
I have setup a profile and account for sending mail using DatabaseMail. I have a SQL JOB. If the job fails, I receive an Email.
Till this point, everything works fine. This is what the email looks like :
JOB RUN: 'GenerateJVForLabourAndOverheads_R11Testing' was run on 20-12-2012 at 10:10:50
DURATION: 0 hours, 0 minutes, 0 seconds
STATUS: Failed
MESSAGES: The job failed. The Job was invoked by Schedule 58 (Execute SP). The last step to run was step 1 (Execute SP).
Now what I want is, if the job fails for any reason, that error message should appear in the email message body.
for example, FK_Constraint error , Conversion errors or any error that caused my sql job to fail.
Is this possible ?
Any help appreciated,
Thanks,
Lok..

This is one way to do, assuming your job has 2 steps and step 1 does the main part.
So,in your step 2 of the job, you can add the below code and
declare @body1 varchar(8000)
select top 1 @body1 = [Message] from msdb.dbo.sysjobhistory A INNER JOIN msdb.dbo.sysjobs B ON B.Job_id = A.Job_id
where B.Name = <<JobNaMe>> and A.step_id =1 order by instance_id desc
EXECUTE msdb.dbo.sp_send_dbmail @profile_name = <<YourMail profile>>
,@recipients = <<RecipeintEmail>>,@subject =<<Your subject>>,@body = @body1
I guess, you can also log the job step output to an outputfile and have it sent as an attachment to your mail... this might help if you have many steps in one job....
HTH!!
Please mark as 'Answer', if the solution solves your problem.

EXECUTE permission denied on sp_sqlagent_log_jobhistory when running a maintenance task or sql job

Hi folks,
I have a scheduled maintenance plan and associated jobs in SQL Server 2008 SP2 that have been working but stopped about two months ago. When I run a maintenance task or sql job using any account (sa, sysadmin-priveleged domain account, etc) I get the following
entries in the SQL Server Agent log (see below). I've tried changing the SQL Server Agent account, applied the latest hotfixes (CU2 for 2008 SP2) and set permissions manually so that the service accounts have dbo access to the msdb database. Anyone got other
ideas? I've avoided recreating the msdb database, but that may be my only option.
Date  4/02/2011 3:42:40 PM
Log  SQL Server Agent (Current - 4/02/2011 3:23:00 PM)
Message
[298] SQLServer Error: 229, The EXECUTE permission was denied on the object 'sp_sqlagent_log_jobhistory', database 'msdb', schema 'dbo'. [SQLSTATE 42000] (ConnExecuteCachableOp)
Date  4/02/2011 3:42:40 PM
Log  SQL Server Agent (Current - 4/02/2011 3:23:00 PM)
Message
[298] SQLServer Error: 229, The EXECUTE permission was denied on the object 'agent_datetime', database 'msdb', schema 'dbo'. [SQLSTATE 42000] (ConnExecuteCachableOp)
Date  4/02/2011 3:42:40 PM
Log  SQL Server Agent (Current - 4/02/2011 3:23:00 PM)
Message
[298] SQLServer Error: 229, The EXECUTE permission was denied on the object 'sp_sqlagent_log_jobhistory', database 'msdb', schema 'dbo'. [SQLSTATE 42000] (ConnExecuteCachableOp)

And just to add to the confusion - I created a SQL login called sql-maintjobs and have it sysadmin priveleges. I then logged in to SQL using this account on the instance that is failing and ran the following:
declare
@backupjobid uniqueidentifier
select
@backupjobid=CONVERT(uniqueidentifier,
'2C4974D4-53BE-4E38-8EC0-8F5398CADE88')
exec
sp_sqlagent_log_jobhistory
@job_id = @backupjobid,
@step_id
=1,
@sql_message_id
= 0,
@sql_severity
= 0,
@message
=
NULL,
@run_status
=1,
-- SQLAGENT_EXEC_X code
@run_date
=19900101,
@run_time
=1,
@run_duration
=1,
@operator_id_emailed
= 0,
@operator_id_netsent
= 0,
@operator_id_paged
= 0,
@retries_attempted
=0,
@server
=
NULL,
@session_id
= 0
This sql worked fine - no permission errors at all. That would suggest the account does have permission to EXECUTE that stored procedure... very confusing!

How to call a stored procedure on time basis with out using sql job and GOTO

Hi,
I wanted to call a stored proc, on time basis ,
please tel me how it can be done with out using sql job , goto .
1) That is, is there any timer aviable in sqlserver.
q2) And which one is better GOTO or sql job.
yours sincerley

Raj, Check if my explanation helps you:
Your job runs every 10 seconds.
Lets say first time you are scheduling and running your job at 12:00:00 PM
Now your proc will start executing.
Say it got finished at 12:00:07.
Now the next schedule time is 12:00:10 PM.
The moment this time hits, the job will get invoked and start executing the proc.
Lets say this time it finished at 12:00:22 PM (It took 2 extra seconds)
This time the scheduled time is already gone (12:00:20 PM), thus it'll now run at the next schedule that is 12:00:30 PM.
Thus if anytime your job takes more than 10 seconds to run, it'll just miss those particular schedules overlapping with execution time. Otherwise you are good to go.
PS: A job is the best way to handle this, in your problem statement you don't need a job but that would be wrong. You have another way to do that, if you keep running your procedure all the time and the moment your timestamp hits a multiple of 10
seconds you can run your logic and then returning to the timer. But this is extremely wrong for a system. Even if your requirement is extremely transactional and complex, I would not suggest this. If the job is taking more than 10seconds (which it might if
your logics inside are complex), you should optimize your code and table architecture.
Chaos isn’t a pit. Chaos is a ladder. Many who try to climb it fail and never get to try again. The fall breaks them. And some are given a chance to climb, but they refuse. They cling to the realm, or the gods, or love. Illusions. Only the ladder is real.
The climb is all there is.

Job owner are set to users those no longer with the organization

Hello,
I was reviewing the currently list of job owners in my organization and found a lot of them are set to users or people who have left the organization.
Could anybody advice if there would be any impact of this?
Best regards,
Mohan

The jobs may start failing when their AD accounts are removed. If the users have left it is better to change the job owner to a different account.
To ensure such issues wont happen, it is better to create a generic AD account with only necessary permissions and use it dedicately for this purpose.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Credential problem while running with SQL job agent

Hi,
SQL job agent fails to run when I change my computer login (Password) credentials information often.
How I can run the SQL job agent with Database login credentials.
Regards
Venkatesh S

Hi Venkatesh,
If I understand correctly, you are using a proxy account has your login credential to run a step of SQL Agent Job. So when you change the login’s password, the credential of the proxy account has an expired password, then the proxy account doesn’t work in
your job.
As per my understanding, we can only use SQL Server Agent Service Account or Proxy Account to run the SQL Server Integration Services Package steps in SQL Agent Job. Since the SQL Server Agent Service Account may not have required permissions to access the
resources in the packages, we recommend use Proxy Account. To create Proxy Account, we should create a credential first. To create a credential, we should specify a Windows user account. So we cannot use a SQL Server authentication login to run the job.
A good workaround is use a windows user account with a password that never expire or changes rarely or update the password of credential followed by your login.
Reference:
How to: Automate SSIS Package Execution by Using the SQL Server Agent (SQL Server Video)
How to: Run a Package
How to: Create a Proxy (SQL Server Management Studio
Thanks,
Katherine Xiong
Katherine Xiong
TechNet Community Support

Execute the SSIS packages (2008 version) using SQL job 2008

We need to execute the SSIS packages (2008 version) using SQL job Please help with details information how to execute it.
1.Protection level of the SSIS packages.
2.Configuration File (Curently using XML file)
3.Please provide details how to create Credential (Windows User etc) Do we need to create windows cred explicitly to run the Job etc..
4.Please provide details for creating Proxy.
5.How can we configure the xml file since the xml is reading from local box but when the package is moved from developement box to production box
then the local drive might not be mapped with Production box .
6.Roles that need to be tagged for the Proxy/Credential.
7.Which is the best and safest way to execute ssis packages either msdb deployment or filesystem deployment and other necessary details.

Hi,
If you want to Execute your SSIS package using SQL job then best solution is to first deploy your Package
either using msdb deployment or filesystem deployment.The simplest approach to deployment is probably to deploy to the file system.
So, here is the deployment steps;
There are four steps in the package deployment process:
    The first optional step is optional and involves creating package
configurations that update properties of package elements at run time. The configurations are automatically included when you deploy the packages.
    The second step is to build the Integration Services project to create a package deployment utility. The deployment utility for the project contains the packages that you want to deploy
    The third step is to copy the deployment folder that was created when you built the Integration Services project to the target computer.
    The fourth step is to run, on the target computer, the Package Installation Wizard to install the packages to the file system or to an instance of SQL Server.
you can use below link also;
http://bharath-msbi.blogspot.in/2012/04/step-by-step-ssis-package-deployment.html
After that you need to Schedule package using SQL Agent then Have a look at the following link. It explains how to create an SQL job that can execute an SSIS package on a scheduled basis.
http://www.mssqltips.com/sqlservertutorial/220/scheduling-ssis-packages-with-sql-server-agent/
Deployment in msdb deployment or filesystem deployment has there own merits and demerits.
For security point of view msdb deployment is good.
it provides Benefits from database security, roles and Agent interaction
Protection Level;
In SQL Server Data Tools (SSDT), open the Integration Services project that contains the package.
Open the package in the SSIS designer.
If the Properties window does not show the properties of the package, click the design surface.
In the Properties window, in the Security group, select the appropriate value for the
ProtectionLevel property.
If you select a protection level that requires a password, enter the password as the value of the
PackagePassword property.
On the File menu, select Save Selected Items to save the modified package.
SSIS Provide different Protection levels;
    DontSaveSensitive
    EncryptSensitiveWithUserKey
    EncryptSensitiveWithPassword
    EncryptAllWithPassword
    EncryptAllWithUserKey
    ServerStorage
For better undertsnading you can use below link;
http://www.mssqltips.com/sqlservertip/2091/securing-your-ssis-packages-using-package-protection-level/
Thanks

Sql job - multiple queries in one step

Hello,
In my SQL job, if I have 2 or more stored procedures in a Single step, will it be synchronous call to each SP or all SP will run parallel?
Thanks,

Hello,
In my SQL job, if I have 2 or more stored procedures in a Single step, will it be synchronous call to each SP or all SP will run parallel?
Thanks,
It will execute the queries (sp calls) sequentially
Please Mark This As Answer if it solved your issue
Please Vote This As Helpful if it helps to solve your issue
Visakh
My Wiki User Page
My MSDN Page
My Personal Blog
My Facebook Page

Server Execution ID from SQL Job

Hi,
I have parent and child package architecture where in i m using ServerexecutionID to find status of each packages and if any child package/s fails , i am stopping all packages for further execution. Problem here is , when i run the packages from catalog
, all packages works fine and i am able to read ServerexecutionID , but same is not available when i create a SQL job.
SQL jobs i am running through SQL server agent job.
I m not understanding why i am not able to read ServerexecutionID by SQL job.
Please suggest.
Thanks.

Hi Abhijeet,
ServerExecutionID is Execution ID for the package that is executed on the Integration Services server. The default value is zero. The value is changed only if the package is executed by ISServerExec on the Integration Services Server. So only if we run a
package that with SSIS Catalog as the package source via SQL Agent job, we can see the Execution ID in the job.
To find the Execution ID in the job, please refer to the following steps:
Right-click the SQL Server Agent job in Object Explorer and then click View History.
Locate the job execution in the Log file summary box, view the details of the message for the job step.
Locate the Execution ID listed in the message.
Then we can view the detail information about this package execution with the steps below:
Expand the Integration Services Catalog node in Object Explorer.
Right-click SSISDB, point to Reports, then Standard Reports, and then click All Executions.
In the All Executions report, locate the Execution ID in the ID column. Click Overview, All Messages, or Execution Performance to view information about this package execution.
Reference:
System Variables
Thanks,
Katherine Xiong
If you have any feedback on our support, please click
here.
Katherine Xiong
TechNet Community Support

SQL Job Owners

Similar Messages

Maybe you are looking for