June 14, 2016 at 9:14 am
You say "without affecting the original". Make sure you're selecting "Copy-only backup" so you don't mess up your backup log chain, unless this is going to be part of your normal backup methodology.
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
June 14, 2016 at 9:47 am
subramanian.esakkimuthu 40485 (6/14/2016)
in order to restore the database which is already exits you need to check the mdf ,ldf and ndf (if any) check where is is storing and check the file name should not be same as the old file other wise you will have an issue the file is exist
And you have to use the WITH MOVE option on the restore or it's going to attempt to overwrite the original files.
Again, practice, practice, practice this far away from your production server.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 2 posts - 16 through 16 (of 16 total)
You must be logged in to reply to this topic. Login to reply