You could use dynamic sql in your stored procedure.  It would look sort of like this:

declare @SqlCmd nvarchar(4000)

set @SqlCmd = N'use msdb;exec your procedure'

exec @SqlCmd

hth

Could you post the SQL you are using to restore the database?

Part of the problem could be that you have SQL Server on domain controller.  That alone could take up quite a bit of system resources even if there are only...

You showed us what you are getting and what you want, but you also need to provide us with some sample data as well (preferable the same data used to...

Try this:

declare @month varchar(15)

set @month = datename(mm,dateadd(mm,-1,getdate()))

select @month -- to see what you got

Yes, I could, but I won't.  maybe some one else will, but we aren't doing you any favors just giving you the answers.  You need to take the time to...

This:  If @retval = 0 then successfull, else failure. was a comment telling you that if @retval = 0 then the stored procedure executed successfully, else it failed.

Please try taking...

This:  If @retval = 0 then successfull, else failure. was a comment telling you that if @retval = 0 then the stored procedure executed successfully, else it failed.

Please try taking...

declare @retval int

exec @reval = Load_Audit_Excel.Sp_Start_job @Audit = 'Audit Data Load'

select @retval

If @retval = 0 then successfull, else failure.

Try reading BOL, all of this is there.

For us to help you, you need to show us what you have already done, and what you are trying to accomplish.

The login (user) you are logged in has needs to have grant permission on the stored procedure for you to be able to grant permissions to others.  You either need to...

Even if you want to backup to a network server for failover purposes, I would still do the backup to a local drive and then move it seperately.  The backup...

I'm not a network person, but it looks like you have lost connection to the remote server you are trying to backup the database to.  If you have the space,...

Do you need point-in-time recovery of your database or is a single nightly backup good enough for your purposes.  If you don't need point-in-time recovery, change your recovery mode to...

If your database is in Full Recovery Mode, as I assume, just completing a full backup nightly is the reason your transaction log is getting so big.  Full backups and...