Viewing 15 posts - 76 through 90 (of 405 total)
You can try adding execute as owner while creating the procedure, so that the user can impersonate your permissions.
August 15, 2016 at 5:55 am
The agent jobs and schedules are stored in msdb database. So if you can restore the msdb, you can get the job back.
August 15, 2016 at 5:48 am
If you have a backup of msdb, you can restore it in a development box and try scripting out the job.
August 15, 2016 at 5:25 am
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.
August 12, 2016 at 9:56 am
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...
August 12, 2016 at 3:31 am
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.
August 1, 2016 at 3:47 am
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
August 1, 2016 at 3:25 am
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...
July 29, 2016 at 7:43 am
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...
July 29, 2016 at 6:43 am
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...
July 29, 2016 at 4:59 am
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:
July 29, 2016 at 4:42 am
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...
July 28, 2016 at 8:10 am
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.
July 27, 2016 at 9:37 am
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....
July 27, 2016 at 8:33 am
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...
July 27, 2016 at 5:06 am
Viewing 15 posts - 76 through 90 (of 405 total)