SQLServer won't recognize copied database

  • I copied my mdf and ldf file to the cloud server, and the data path is correct. But the database does not show up in management studio. I have done this before between in house servers running SQL2008. Could it be ownership, permissions, or that the server has another name, or something else.? It is a big file (130GB) that takes 4 days to upload via RDP so I dont want to create a database on the cloud and then import it.

  • Why don't you create the DB on the cloud and restore it from a backup (which might be compressed if you're on 2008R2+). It seems safer than using mdf and ldf files.

    Luis C.
    General Disclaimer:
    Are you seriously taking the advice and code from someone from the internet without testing it? Do you at least understand it? Or can it easily kill your server?

    How to post data/code on a forum to get the best help: Option 1 / Option 2
  • fkarmally (6/19/2014)


    I copied my mdf and ldf file to the cloud server, and the data path is correct. But the database does not show up in management studio. I have done this before between in house servers running SQL2008. Could it be ownership, permissions, or that the server has another name, or something else.? It is a big file (130GB) that takes 4 days to upload via RDP so I dont want to create a database on the cloud and then import it.

    You can't just copy the files and expect SQL to notice. You will need to attach the files to a (new) database. In SSMS, right click on "Databases" and select attach.

  • happycat59 (6/19/2014)


    fkarmally (6/19/2014)


    I copied my mdf and ldf file to the cloud server, and the data path is correct. But the database does not show up in management studio. I have done this before between in house servers running SQL2008. Could it be ownership, permissions, or that the server has another name, or something else.? It is a big file (130GB) that takes 4 days to upload via RDP so I dont want to create a database on the cloud and then import it.

    You can't just copy the files and expect SQL to notice. You will need to attach the files to a (new) database. In SSMS, right click on "Databases" and select attach.

    Exactly!

    The other way is to copy over a backup and restore that.

Viewing 4 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic. Login to reply