JoshDBGuy (2/18/2013)
Copying was an easy way to make a replica of another test database. Because we don't backup every database, if I didn't do a copy, I would have to make a backup and then do a restore. I realize this isn't a big deal but I found the copy functionality (as I'm a DBA in training) and wanted to try it out. If it's not a good idea, I'll make that recommendation going forward but in the meantime I ran into these errors. I'm concerned that there may be some underlying problem with one of our drives (as this is a brand new server) but if the copy feature is unreliable, I can attribute it to that and move on.
Copy is not a good idea, at least thats my opinion, if you want to send an point in time copy try replication or snapshots. Also if you go for the backup and restore create an SSIS that way you can schedule it.
MCSE SQL Server 2012\2014\2016