Re: Trouble moving db to another sql2005

Well, the easiest way I have found to do this is to detach it
from one SQLServer (right-click on the database in the Management
Studio and choose Detach), copy the mdf and ldf files to to wherever
you want them, and attach the database (right-click on Databases
in the Management Studio and select Attach) in the new SQLServer.

I think this will work for you.
Good luck.
Robin S.
----------------------------------
"dgk" <dgk@xxxxxxxxxxxxx> wrote in message
news:2ialo21spkclj14sm6otiunnmpqnk4rjjl@xxxxxxxxxx
I'm trying to copy a database from my machine's SQLServer2005 to a
production machine. I tried a restore from backup, which gave me an
error that the on disk structure was 611 and the production machine
supports 539. I've looked around and found similar problems, but those
were all involving SQL2000. These are both 2005. Oddly, the management
console of the production machine is version 9.00.2047.00, indicating
it's later than my machine's 9.00.1399.00. But that is the console,
not the db version, which I can't find.

My admin says that there is a big patch (or service pack) that
surprisingly isn't on the production machine and he'll do that
tonight. Does anyone know if that will cure the problem?

I don't even know if a restore will actually accomplish my goal of
getting the db into production. As you can tell, I'm not SQL2005
expert.

The db in question is the one that handles the authentication and user
profiles for asp.net version 2 (aspnetdb.mdf). I wrote the app using
sqlexpress am an now moving it to sqlserver. It works fine on my
machine and a test server, but apparently the production server is a
bit behind the times.

Any advice appreciated. I tried the script wizard but have no idea how
to use that.


.

Relevant Pages

  • Re: Trouble moving db to another sql2005
    ... from one SQLServer (right-click on the database in the Management ... Studio and choose Detach), copy the mdf and ldf files to to wherever ...
    (microsoft.public.sqlserver)
  • Re: Informix 7.30 (I know!)
    ... >We have a need to migrate the database from a running Production server on ... >to a Pre Production machine which will eventually replace the Production ... Wasn't "no downtime", but the total downtime was very ...
    (comp.databases.informix)
  • Informix 7.30 (I know!)
    ... We have a need to migrate the database from a running Production server on to a Pre Production machine which will eventually replace the Production Machine. ... We plan to take level "0" back from the Old box, restore to the new box and then apply the delta using scriptsto bring the data in sync. ... Is there a way by which after we have taken a level "0" backup, we can then take another backup of whatever changed after level "0" and apply that to database using some informix utility.I am not sure if a Level "1" will do the job as while the Level "1" is being restored we will have a down time. ...
    (comp.databases.informix)
  • Migrating from ? to Oracle
    ... I'm going to be working on a Perl app using a database through the DBD ... The end production machine will run Oracle for which ... we don't have access to Oracle locally and wish to use a ... functions of the various DBI drivers that would be great. ...
    (perl.dbi.users)
  • Re: Change datatype on all table (HELP, HELP, rush)
    ... You will want to test this before running it on a production machine to make ... sure that you do not loose any data... ... > I need a way to change a datatype from nvarchar to varchar on all tables ... > within a database. ...
    (microsoft.public.sqlserver.programming)