Viewing 15 posts - 2,011 through 2,025 (of 19,564 total)
whereisSQL? (9/24/2014)
SQLRNNR (9/24/2014)
BWFC (9/24/2014)
Ouroborosburro de oro
burrito
burr filled dough
September 24, 2014 at 10:39 am
sestell1 (9/24/2014)
Arrrrr.... it be a shame ta not be postin' this question on September 19!
+10
Missed opportunity thar
September 24, 2014 at 8:17 am
Ed Wagner (9/24/2014)
Sean Lange (9/24/2014)
Ed Wagner (9/24/2014)
TomThomson (9/24/2014)
BWFC (9/24/2014)
BiteBark
Tree
Pith
Pithy
Python
September 24, 2014 at 7:43 am
If this were an actual disaster recovery, then you would want a tail log backup. But that isn't the case here.
You might want to read up on a few...
September 23, 2014 at 4:17 pm
It is because you did not specify the replace key word.
September 23, 2014 at 4:15 pm
Tail log backup is not necessary on the target before you do a restore.
The replace let's it know you are "replacing" the database with the backup you specified.
September 23, 2014 at 4:06 pm
Try this instead
Restore database Test1
from disk ='\\Test\DBdumps\test1.bak
with recovery,replace
September 23, 2014 at 3:35 pm
Alter the database and perform the restore from the master database.
September 23, 2014 at 2:45 pm
After you restore the database you will want to ensure it is back to multi_user mode.
September 23, 2014 at 1:59 pm
Have you confirmed that the path is reachable from your server?
September 23, 2014 at 1:43 pm
Restricted user just changes it so only users with elevated perms can access the database. It does not prevent multiple connections from being established and preventing the restore.
You will...
September 23, 2014 at 1:09 pm
ramana3327 (9/23/2014)
Correct me my understand is wrongso compare to the copy the backup into the local and restore, it is better to restore from network
No. It is better to...
September 23, 2014 at 12:28 pm
Viewing 15 posts - 2,011 through 2,025 (of 19,564 total)