syntax is wrong, use following

exec msdb..sp_send_dbmail

@profile_name = 'Chandhra_local',@recipients='cshekhar@agilitylogistics.com'

, @subject ='Log Shipping Backup Job succeeded'

, @QUERY = 'select top 7 j.name as Jobname,jh.message, run_status, run_date, Run_time

from msdb.dbo.sysjobhistory jh

join

msdb..sysjobs j

on j.job_id=jh.job_id

where...

Ok..

I have 3 files

1. abc.cmd - This is the batch file we will call from DOS prompt

[font="Courier New"]for /f %%a in (srvlist.txt) do osql -E -S %%a -i...

check your dbmail setup, you should have one profile set to default .. if not you can use

@profile_name = 'valid profile name'

in sp_send_dbmail statement. (check BOL for sp_send_dbmail...

and the only difference is for each single quote (') in query, you have to use two single quotes('')

exec msdb..sp_send_dbmail @recipients='youmail@name.com'

, @subject ='your suject goes here'

, @QUERY = 'select top 7 j.name as Jobname,jh.message, run_status, run_date, Run_time

from msdb.dbo.sysjobhistory jh

join

msdb..sysjobs j

on j.job_id=jh.job_id

where j.name...

It means its already in sys.servers list

please run

select * from sys.servers

and see if that server already in list.

In my organization, we come across such situation very frequently, we have some 500+ servers running across globe. We mix DOS batch script with sql query.

1. Batch will open connection...

Also please note that in sql server 2k5 management studio can register both sql 2k and sql 2k5 servers. So dont get confused.

try osql and see what error you are getting

osql -E -S server_name

or

osql -U username -P password -S servername

It seems you have forcefully registered that server in enterprise...

This NT Authority\Anonymous LOGON error can be related to kerberos setting. Please check spn (setspn /L) to verify (blogs.msdn.com/sql_protocols/archive/2005/10/12/479871.aspx). Please consult your SA.

The best workaround is not using nt...

Are both servers 2k5?

I dont know exactly, but I have seen the same situation, 2k server was creating as system SP while 2k5 was taking same code as user...

Check this article

http://www.sqlservercentral.com/articles/Administration/creatingasystemstoredprocedure/1358/

As someone already replied, mostly DBA are not responsible for deciding backup...

Some application connections are persistent in nature, so if you simply kill them they will come again in no time.

alter database [your_db_name] set offline with rollback immediate

Then drop...

Another usually found is - QA server

Some application also use - Staging server