Sql agent jobs based on the database and the user

Dear All,
I have a requirement of configuring an user who should only have access to one database out of all and also able to create, view and modify sql agent jobs only for the allowed database. For allowing to see the selected database to particular user I have
granted permissions as per below,
create LOGIN mhtc WITH PASSWORD='mhtc', CHECK_POLICY = OFF;
USE master;
GO
DENY VIEW ANY DATABASE TO mhtc;
USE master;
GO
ALTER AUTHORIZATION ON DATABASE::MHTC TO mhtc;
GO
but user not able to see sql agent jobs so I want to give necessary permission to this user to view,create and modify sql agent jobs only in allowed databases. Basically I want to separate users from each database and separate sql agent jobs based on the
user and database.
Your expert advices are highly appreciated.
Thanks,
Manjula

I want to give necessary permission to this user to view,create and modify
sql agent jobs only in allowed databases.
Hello Manjula,
SQL Server Agent Jobs are not created / dedicated for a user database. The Jobs are store in System database "msdb".
See
Implement SQL Server Agent Security for Details about required permissions.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Similar Messages

SQL Agent Job failing - not using credentials in the config file for Data source

Hi
We have an SSIS pkg, that is secheduled as SQL Agent job using proxy account. The pkg contanins data source for connecting different SQL servers and the proxy account do not have access to the external DBs. The data source credentials are stored in the Config
file.
Why the job is not using the credentials in the config file and try to use the proxy account and failing.
Do the proxy account need access to all the external dbs in the pkg, and then what is the purpose of the config file.
I am sorry, i am not SSIS person trying to understand. If any one can explain tha will be great!!
Thank you!
VR

Please take a look at these URLs:
Schedule a Package by using SQL Server Agent
SSIS package does not run when called from a SQL Server Agent job step
Cheers,
Saeid Hasani
Database Consultant
Please feel free to contact me at [email protected] as well as on Twitter and Facebook.
[My Writings on TechNet Wiki] [T-SQL Blog] [Curah!]
[Twitter] [Facebook] [Email]

I am using the database connectivity toolkit to retrieve data using a SQL query. The database has 1 million records, I am retrieving 4000 records from the database and the results are taking too long to get, is there any way of speeding it up?

I am using the "fetch all" vi to do this, but it is retrieving one record at a time, (if you examine the block diagram) How can i retrieve all records in a faster more efficient manner?

If this isn't faster than your previous method, then I think you found the wrong example. If you have the Database Connectivity Toolkit installed, then go to the LabVIEW Help menu and select "Find Examples". It defaults to searching for tasks, so open the "Communicating with External Applications" and "Databases" and open the Read All Data. The List Column names just gives the correct header to the resulting table and is a fast operation. That's not what you are supposed to be looking at ... it's the DBTools Select All Data subVI that is the important one. If you open it and look at its diagram, you'll see that it uses a completely different set of ADO methods and properties to retrieve all the data.

Backing up the database and the limitations

Hello all,
I tried to follow the steps in the documentation to back up the database;
On Windows: Click Start, point to Programs, point to Oracle Database 10g Express Edition, and then select Backup Database
but I dont see Backup Database under Oracle database 10g express, here is what I have there:
Get Help >
Get Started
Go To Database Home Page
Run SQL Command Line
Start Database
Stop Database
Thats all.
What I am trying to check is, if I can change the location for backups to avoid the 2 backup limitation. Is it possible to do that?

Well - this is the area we are having a lot of internal discussions on - so this is not final yet, but feedback would be a good thing.
Lets say you shut the machine down mid transaction one night while there are still users connected. This would not cause disk corruption, but you had inflight transactions at the time. On restart, the database would automatically roll forward the committed transactions, and automatically rollback uncommited transactions. So your database would be consistent. You would of course lose the transactions that were uncommited. This is what we call instance recovery.
Lets say you take a backup on Monday, using the techniques we are proposing. On Tuesday the disk crashes and dies. You are not using Raid 5 etc, so you have no disk based mirror of your data. So you go and buy a new disk, add it to the machine, re-install the database software, and then restore from Monday nights backup. This is what we call media recovery.
Using the techniques we propose for Oracle Database XE, you will lose ALL transactions from the time of the backup (i.e Tuesday) - both committed and uncommited until you complete the restore.
If you did not want to run the risk of losing transactions in the event of a disk crash, then you should look at one of the licensable versions, which uses a technique called archive logging to allow you to roll forward all transactions since your last (or any given backup).
Note that for all versions however, backup is online.
Thoughts ?

ORA-07445: exception encountered in the database and the databasde wentdown

Hi,
I got the eblow errors in the alert log file. and the database went donw after this errors. Can anybody suggests the cause of the error.
Errors in file /ORADATA/proddb/9.2.0/admin/PROD_dgoracluster/udump/prod_ora_17784.trc:
ORA-07445: exception encountered: core dump [kssrem()+177] [SIGSEGV] [Address not mapped to object] [0x4] [] []
ORA-03135: connection lost contact
Tue Jan 19 11:31:49 2010
Errors in file /ORADATA/proddb/9.2.0/admin/PROD_dgoracluster/udump/prod_ora_17784.trc:
ORA-07445: exception encountered: core dump [kghssgmm()+83] [SIGFPE] [Integer divide by zero] [0xAD0357D] [] []
ORA-07445: exception encountered: core dump [kssrem()+177] [SIGSEGV] [Address not mapped to object] [0x4] [] []
ORA-03135: connection lost contact
Tue Jan 19 11:31:51 2010
Errors in file /ORADATA/proddb/9.2.0/admin/PROD_dgoracluster/bdump/prod_pmon_4625.trc:
ORA-07445: exception encountered: core dump [kggchk()+72] [SIGSEGV] [Address not mapped to object] [0x17] [] []
Tue Jan 19 11:31:55 2010
MMON: terminating instance due to error 472
Instance terminated by MMON, pid = 4643
Thanks,
Prashanth.

hi, initially you can check trace files also to get to know what the problem is.
you can look in metalink for ora-600 lookup tool which provides information for ora-7445 errors also.
if not found anything, then raise a SR with oracle support

Change unix owner for the database and the binaries

Hello,
Do you guys know of any documents, from Metalink or other sources that
would lay out all the steps needed to take one database from one set of
binaries owned by a unix user to another set of binaries owned by
another unix user? The new unix user will also own the database files as
well.
Thank you all very much,

You may change all oracle owned files recursively, but you should be aware of the files that belong to the root user, those have SUID's enabled, and if you change the owner, networking functions won't work, among other features.
Are you planning to change the group too? or just the owner?
~ Madrid

Management Studio Crashing When Adding SSIS Step to SQL Agent Job

Hi
I am running Windows Server 2012, SQL Server 2012 SP2 CU2, SQL Server Management Studio 2012 and Visual Studio 2012.
I have existing SQL Agent Jobs that run SSIS packages and they all currently work. However, if I try to edit them or add a new job that uses a SSIS package Management Studio will crash. I was having this problem a couple weeks ago when I was still
on SQL Server 2012 SP1 CU9, so I updated to SQL Server 2012 SP2 CU2 and the problem went away for a couple weeks and I was able to add new SQL Agent jobs that run SSIS packages. But now it issue is back and there are no new updates to try and fix it.
Has anyone seen this before and found a reliable fix to it?
Steps to cause crash:
1) Open new SQL Agent Job
2) Select Steps and add a New Step
4) Change the job type to SQL Server Integration Services Package.
5) SSMS Crashes
Error Message Below:
===================================
The type initializer for '<Module>' threw an exception. (SqlManagerUI)
Program Location:
at Microsoft.SqlServer.Management.SqlManagerUI.DTSJobSubSystemDefinition.Microsoft.SqlServer.Management.SqlManagerUI.IJobStepPropertiesControl.Load(JobStepData data)
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.UpdateJobStep()
at Microsoft.SqlServer.Management.SqlManagerUI.JobStepProperties.typeList_SelectedIndexChanged(Object sender, EventArgs e)
at System.Windows.Forms.ComboBox.OnSelectedIndexChanged(EventArgs e)
at System.Windows.Forms.ComboBox.WmReflectCommand(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.SendMessage(HandleRef hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.Control.SendMessage(Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.Control.ReflectMessageInternal(IntPtr hWnd, Message& m)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.UserControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.CallWindowProc(IntPtr wndProc, IntPtr hWnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at System.Windows.Forms.NativeWindow.DefWndProc(Message& m)
at System.Windows.Forms.Control.DefWndProc(Message& m)
at System.Windows.Forms.Control.WmCommand(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ComboBox.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at Microsoft.SqlServer.Management.SqlManagerUI.JobSteps.newJobStep_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at System.Windows.Forms.Application.ComponentManager.System.Windows.Forms.UnsafeNativeMethods.IMsoComponentManager.FPushMessageLoop(IntPtr dwComponentID, Int32 reason, Int32 pvLoopData)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.RunDialog(Form form)
at System.Windows.Forms.Form.ShowDialog(IWin32Window owner)
at System.Windows.Forms.Form.ShowDialog()
at Microsoft.SqlServer.Management.SqlMgmt.RunningFormsTable.RunningFormsTableImpl.ThreadStarter.StartThread()
===================================
The C++ module failed to load.
(DTEParseMgd)
Program Location:
at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
at .cctor()
===================================
Index was outside the bounds of the array. (DTEParseMgd)
Program Location:
at _getFiberPtrId()
at <CrtImplementationDetails>.LanguageSupport._Initialize(LanguageSupport* )
at <CrtImplementationDetails>.LanguageSupport.Initialize(LanguageSupport* )
Thanks,
Anthony

I ended up being able to work around this without having to recreate everything on a Windows Server 2008 R2. I did this by setting up an azure point to site VPN from
my computer to the Windows Server 2012 hosted on azure. I was then able to connect SSMS from my computer to the Azure VM allowing me to create and edit new SQL Agent jobs that run SSIS packages. Here are the steps to do this
1) Connect to the VPN from another machine besides the server.
2) Open SSMS using the runas.exe command with the Domain\User Name of a Windows account on the server.
- Ex. Runas.exe /netonly /user:DOMAIN\USER "C:\Program Files (x86)\Microsoft SQL Server\110\Tools\Binn\ManagementStudio\Ssms.exe"
2) Connect to the VM's Database Engine using its internal IP address and the port that SQL Server is listening on (default is 1433) and a SQL Login
setup on the server.
-Ex IP, 10.0.0.1,1433
3) Create a new job with the type SQL Server Integration
Services Package. Select the package source (SSIS Catalog). I could not get the server to be automatically discovered here so enter the server’s internal IP address and select the package you want to run.
4) Right click the new SQL Agent Job and choose Script Job As, CREATE To, New Query Window. This is the script to create the
SQL Agent Job and it needs to be edited to contain the Name of the server on the internal IP address that was used earlier.
5) Edit the @command= line of the script to use the server name. Change the highlighted part below to the server name.
- Ex . @command=N'/ISSERVER "\"\SSISDB\PACKAGELOCATION\"" /SERVER
"\"10.0.0.1\"" /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E',
- Change to this
- @command=N'/ISSERVER "\"\SSISDB\PACKAGELOCATION\""
/SERVER SERVERNAME /Par "\"$ServerOption::LOGGING_LEVEL(Int16)\"";1 /Par "\"$ServerOption::SYNCHRONIZED(Boolean)\"";True /CALLERINFO SQLAGENT /REPORTING E',
6) Now change the name of the package in the script and run it. Now the new package can be edited in the GUI to change things like the schedule and alerts. Also you
can edit any existing packages.

Automated SQL Agent jobs do not run

Hi all
I am having serious issues in running SSIS packages automatically.
Furthermore, when I assign a job to run the SSIS package manually (SSMS -> Start Job at Step....), it runs through the job very quickly and displays "success", when in actual fact, it hasn't done anything.
I have tested my package in BIDS and all works fine.
Can anyone give me a clue as to what may be going wrong please?
Many thanks in advance.

Hi divvyboy,
Based on your description, the issue may be caused by one of the following factors:
Data source connection issue. This can occur because the SQL Server Agent Service Account or the proxy account lacks permissions to access the data source.
Package Protection Level issue.
For the solution in each scenario, please refer to the following link:
http://social.technet.microsoft.com/Forums/sqlserver/en-US/e13c137c-1535-4475-8c2f-c7e6e7d125fc/how-do-i-troubleshoot-ssis-packages-failed-execution-in-a-sql-agent-job?forum=sqlintegrationservices.
If the issue persists, please post the error details from the SQL Server Agent job history.
Regards,
Mike Yin
TechNet Community Support

Can't edit SQL Agent job step

Hello. In SQL 2005 Enterprise I've added a user to SqlAgentUseRole in msdb. They can create a job but cannot later go back and edit a step; everything is grayed out. I saw this article about an error in SQL 2008 that's been fixed in 2008 CU3.
http://support.microsoft.com/kb/2315727
I'm not sure if this is the same issue. If it's a different issue, does anyone know if it's been addressed in SQL 2012?
Ken

This issue is due to limited rights on SqlAgentUseRole in msdb, user can Create/modify/delete only owned jobs
As mentioned in below link:
http://technet.microsoft.com/en-us/library/ms188283.aspx
Further, provide access on some msdb procedures as discussed in below thread:
sp_update_job
sp_update_jobschedule
sp_update_jobstep
http://social.msdn.microsoft.com/Forums/en-US/c62b61a0-7f66-4cb9-a5a6-577d5f73e8aa/permissions-to-modify-sql-agent-jobs?forum=sqlsecurity
Please click the Mark as answer button and vote as helpful if this reply solves your problem

Is there any character set translation facility between the database and th

We are upgrading a character based SQLforms version 3 application to forms6i running over the web against a 9.02 database.
Is there any character set translation facility between the database and the Forms server / web browser?
Our database character set is NEE..P4 (North European). However, the user needs to see the data in the BLT..P13 (Baltic) character set.
In the old application, users accessed these forms through a telnet client and this did the translation. For example :
The database character :
� (Unicode hex value = 00D0)
would be translated by and displayed on the telnet client as :
� (Unicode hex value = 0160)
A colleague of mine has done some experimenting. By changing the NLS_LANG registry setting to BLT..P13 in his oracle home and loading the Baltic character set for his Windows 2000 environment, he has been able to achieve the same translation in SQLPLUS.
However, we have been unable to do the same in a forms web runtime.

Oracle automatically translates characters between the display CharacterSet and the database characterset
The statement
In the old application, users accessed these forms through a telnet client and this did the translation
worries me a little because it implies that the data you have stored in the database might not actually encode the characters that you think you've put in.
This aside you need to set you NLS_LANG parameter on the application server for the client side character set - if you are using the forms listener servlet architecture then this would be set in the default.env file.

How do I automatically backup SQL Agent jobs and SSIS packages on the mirror daily?

I have seen this question asked before but I could not find a satisfactory answer. What is the best solution to get your SQL Agent jobs/schedules/etc. and your SSIS packages on the mirror server? Here's the details:
Server A is the principal with 2 DBs mirrored over to server B. Everything is fine and dandy, DBs are synched and all good. In Disaster Recovery testing, we need to bring up server B, which now will serve as the principal. Server A is inaccessible. Now,
we need all our jobs that are setup in server A to be in server B, ready to go, but disabled. We also need all our SSIS packages properly stored. Yes, we store our packages in the MSDB in server A.
Now, I can see a few answers coming my way.
1- Backup the MSDB to server B. When you bring server B up as principal in DR, restore the MSDB. All your jobs,schedules,steps, SSIS packages will be there. Is this possible? Can this be done on server B without rendering it incapable of serving as the principal
for the mirrored DBs? My fear with this option is that there may be information in the MSDB itself about the mirroring state of the DBs? Or is all that in the Master DB? Have you tried this?
2- Right click each job, script them out, re-create them on server B... No, thank you very much. :) I am looking for an AUTOMATED, DAILY backup of the jobs and SSIS packages. Not a manual process. Yes, we do change jobs and packages quite often and doing
the job twice on two servers is not an option.
3- Use PowerShell.. Really? Are we going back to scripting at the command prompt like that, that fast?
Since I fear option number 3 will be the only way to go, any hints on scripts you guys have used that you like that does what I need to do?
Any other options?
Any help GREATLY appreciated. :-) I can be sarcastic but I am a good guy..
Raphael
rferreira

I would go with option number 3. Once you have a script simple run it....
param([string]$serverName,[string]$outputPath)
function script-SQLJobs([string]$server,[string]$outputfile)
[reflection.assembly]::LoadWithPartialName("Microsoft.SqlServer.Smo") | Out-Null
$srv = New-Object Microsoft.SqlServer.Management.Smo.Server("$server")
$db = New-Object Microsoft.SqlServer.Management.Smo.Database
$scrp = New-Object Microsoft.SqlServer.Management.Smo.Scripter($srv)
$scrp.Options.ScriptDrops = $FALSE
$scrp.Options.WithDependencies = $TRUE
$jobs = $srv.JobServer.get_Jobs()
$jobs=$jobs | Where-Object {$_.Name -notlike "sys*"}
foreach($job in $jobs)
$script=$job.Script()
$script >> $outputfile
"GO" >> $outputfile
---script-SQLJobs "SQLSRV12" "C:\Jobs\test.txt"
Best Regards,Uri Dimant SQL Server MVP,
http://sqlblog.com/blogs/uri_dimant/
MS SQL optimization: MS SQL Development and Optimization
MS SQL Blog:
Large scale of database and data cleansing
Remote DBA Services:
Improves MS SQL Database Performance

Getting error while trying to upload the data in excel from SSIS package through sql agent job

We are getting below errors.
Error:
The Microsoft Jet database engine cannot open the file '\\serversdev\Documents\QC Files\Prod.xls'. It is already opened exclusively by another
user, or you need permission to view its data.
Please suggest ASAP
Regards,
Ramu
Ramu Gade

Hi Dikshan Gade,
According to your description, you want to upload data from excel to database, when you call ssis package through SQL Server Agent job, you got the error message.
To troubleshoot the problem, please refer to the following steps:
Validate that the account has permissions on the file and the folder.
Verify that the file and the data source name (DSN) are not marked as Exclusive.
Make sure SQL Server Agent Services service account has the permission to access the database.
We can check SQL Server Agent’s activity logs, Windows Event logs and SSIS logs to get more clues. Also the tool Process Monitor is helpful to track the cause of registry or file access related issues. For more information about the issue, please refer to
the following KB article:
http://support.microsoft.com/kb/306269
If you have any more questions, please feel free to ask.
Thanks,
Wendy Fu
Wendy Fu
TechNet Community Support

How to schedule SQL Agent job for XMLA script file of SSAS database instead of taking a backup.

I want to script XMLA file instead of backup of database and also want to schedule a job for the process in SQL Agent.
Is there any pros and cons when I script the XMLA file of the SSAS db instead of taking a backup ?
Amir

Hi Amir,
You can take the Create SSAS database XMLA script and run the job to create the cube. The script contains the Metadata definition of the Database and it does not contain the actual data.
Pros: Since you are only creating an empty cube the script will run faster
Cons: You still need to process the created cube to use it for reports.
Fastest option is to take the backup of the cube and restore wherever necessary.
And you can also use TFS source control to deploy the cube and process it later.
Regards,
Venkata
Venkata Koppula

Running an SQL Server Agent Job to execute a package but the job FAILS on Connections

I have created a package which basically imports data from one database to another, The database where it collects the data from the job is failing on connecting reporting the following message:
Source: ****** Connection manager "Source - *****"     Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft
OLE DB Provider for SQL Server" Hresult: 0x80040E4D Description: "Login failed for user '*ConnectionONE*'.". End Error Error: 2015-02-18 11:36:04.94     Code: 0xC020801C
Source: Data Flow Task Get Revenue Data [1]     Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "Source - *****" failed with error
code 0xC0202009.
The package runs fine if executed within the package but fails from the SQL Agent Job.
NB * is to hide confidential data. *ConnectionONE* is the database which the package is attempting to get data from.
Completely puzzled on what to do as i have tried reading other forumns but they dont seem to be helping.
Any Help would be great thankyou!

That is because package is set to "EncryptSensitiveWithUserKey". Please change that to "EncryptSensitiveWithPassword" and the provide password to protect sensitive data.
More information
here.
Regards,
Vishal Patel
Blog: http://vspatel.co.uk
Site: http://lehrity.com

SQL Agent Job Notification - Database Mail problem

Hi
I'm a little stumped. Have setup database mail on SQL Server 2008 (SP1 x64) and its working fine except when its supposed to send out a SQL Agent job notification.
I've enabled database mail on SQL Agent and have specified a profile, but when it tries to send an email on agent job completion it errors with "NOTE: Failed to notify '<operator>' via email."
Can anybody help?
Thanks

Hi Webdawg,
As suggested above, try these steps.
1. Try test email first, this can be by done (right click on database mail under mangement folder). prior to that you should already have a profile configured to send the emails and make sure you got the right SMTP server and do not block
port 25.
2.If test is succeeds, enable mail option under sql server agent properties and select 'database mail' and corresponding profile.Add the reciepents email to the operators under sql server agent(check the enabled option here). Restart the SQL sever
here.
3. Create your sql job and in the notifcations section you should see email option and should have the operator email you configured above.
Try it out. let us know. Hope it helps.
If the test succeeds and still you did not get the email from sql job, check the database mail log and check whether it is being queued. let us know.
Please mark as 'Answer', if the solution solves your problem.

Sql agent jobs based on the database and the user

Similar Messages

Maybe you are looking for