You can try adding execute as owner while creating the procedure, so that the user can impersonate your permissions.

The agent jobs and schedules are stored in msdb database. So if you can restore the msdb, you can get the job back.

If you have a backup of msdb, you can restore it in a development box and try scripting out the job.

Thanks for coming back with the clarification.

Looks like your database is mainly read-only not heavily used. So you would be good with a full backup.

The full backup will be good enough to restore it back to a consistent state.

You do not need to do anything separately for the transaction log.

But can you be...

I have faced this same issue long back with replication and solved with rename.

As per the link I shared you you need to reestablish the mirroring with new name.

If you run sp_helpserver the one with id 0 is it still having the old name?

If yes, try renaming this way

https://msdn.microsoft.com/en-us/library/ms143799.aspx

edit: added link

Sean, I think dastagiri is asking about rebuilding indexes.

Unless you give online option, the table will be locked until the clustered index is rebuilt.

With online option there will locks towards...

What issues you got with msforeachdb?

One quick and dirty solution, please make your own changes

IF object_id('tempdb..##AllDBTablesRowcnt') is not null

Drop table ##AllDBTablesRowcnt

Select db_name() DBName,Object_name(object_id) TableName,rows into ##AllDBTablesRowcnt from sys.partitions where...

You should be looking at the section with delete and insert. Two concurrent session got through the delete, may be got page locks due to lock escalation, and both wait...

Somebody once warned me while handing over a CD that had been in the shelf for so long

"Be careful it might have caught some virus" :hehe:

So the current active version is server 2. This might have moved on with new transactions from application

so you need to sync server 1 first. To minimize down time you...

Create event handler for OnError for the data flow task set Propagate to false. This will prevent the error from propagating to the foreach loop container.

Hi Ajay,

When you say 'as earlier' if you mean making the primary server to be used back again from your application, you would need to take the database back there....

Where is your DBA? Who created the log shipping in first place.

You have to configure log shipping back again, this might not be very complex, but you should be thorough...