Showing posts with label laptop. Show all posts
Showing posts with label laptop. Show all posts

Monday, March 19, 2012

Move SQL server to SQL server 2005 Express

I'm new in Express Edition.

We use SQL 2000 on our SBS2003.

For disaster recovery I installed SQL Express on a laptop.

How can I move database and application from SQL 2000 to

Eexpress edition?

Many thanks

Peter

One of the easy ways is to just do a backup and recovery, but I would also look at the upgrade adviser and make sure that the application can be upgraded. If you are doing the sharpoint databases from sbs you can use the sql express install system to upgrade the instance.

|||

Glenn.

Did you mean use SQL server 2000 backup utility to backup all Dbs then setup Express Edition, then use its recovery to restore

Dbs? One of my friend suggested just copy all .MDF and .LDF files, then use SQL server Management Studio Express to link them.

We don't use Sharepoint database.

Thank you for your attention.

Welcome your further advise.

Peter

|||

Hi Peter,

Yes, you can backup using SQL 2000 and then restore using SQL Express just as you suggest. You can also just copy your MDF/LDF files into the Data directory for SQL Express and then use Management Studio to Attach those files.

In either case, the resulting database file in SQL Express can not be moved back to SQL 2000, the file formats are not compatible.

Mike

|||

Hi Mike,

Thank you for your advice.It’s important to know “the resulting database file in SQL Express can not be moved back to SQL 2000, the file formats are not compatible.”

My project is for disaster recovery, in case of SBS2003, SQL 2000 running on it, down.

I have to restore database after SQL 2000 server comes back online.It looks like I can’t use SQL Express as backup.

Can I use MSDE? I think its data file format is same to SQL 2000. If it can, could you please let me know how to do that? Do we still need Management Studio to attach database?

Many thanks

Peter

Monday, March 12, 2012

Move sql database from development machine to server with active directory

Hi all! I know I might sound stupid, but I have this problem. I have developed my database on my laptop which does not use Active directory. Lets say I access the database with: SPIDERMAN\DB1 on SQL server, where the name of my laptop is SPIDERMAN, and the database is DB1. Now, I create an SQL script from sql server and make the necessary changes, like changing the computer name to say, SUPERMAN where my deployment server's name is SUPERMAN. But when I run the SQL script on the SUPERMAN server, it gives me an error like: "User or role SUPERMAN\DB1 does not exist in this database". I have deployed databases in this way on servers without Acive directory, so I'm sure its not a mistake on my side. So how am I supposed to go around this active directory thingi! Please help me out! I'm counting on u guys!

WesI am not a guy and not an admin, Microsoft MCDBA requirements but you need the Domain account name used to install SQL Server on that network to run the script ask the Network Admin to give you the info. If there is no SQL Server on the network tell the Admin to create a Domain User account that is configured as a service account so you can install SQL Server with Network permissions because you cannot run Replication in SQL Server if SQL Server is running on the Local Systems account because SQL Server Agent will not have network permissions. Hope this helps.

Kind regards,
Gift Peddie|||Thanks, Gift Peddie! I owe u a lot! But basically, I did not really get a single word you just said! It was like arrows flying over my head! Could you pleeeeeaaaasssse elaborate a little? I would be really grateful!

Thanks anyways.
I really appreciate it.

Wes.|||Thanks I see what you are saying, sorry it must be the holidays. You need the SQL Server System Admin name and pass word to modify your script before you run it. Thanks again. Hope this helps.

Kind regards,
Gift Peddie|||Thanks,
This might help me a bit. I'm understanding it a bit now. (LOL) I can be a real idiot sometimes! Don't mind me!

Regards,
Wes.