Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 397
  • Last Modified:

Moving SQL Database from SEManager to SQL2008 or 5 Express

Hi, I have an older 2003 server running a database on Enterprise Manager.  I want to copy this to either an SQL Express instance on another 2003 server or ideally onto a SQL server running 2008R2.

When I ran a move/copy wizard on the server, but it could not find my other network servers.  So I ran the Register SQL Server Wizard,  it found both or the other instances but an error occurred stating: "to connect to this server you must use sql server management studio or sql server management objects".

Could someone please provide a blow by blow breakdown of how I can accomplish this, with any gotcha's on the database upgrade process so when attached on the new server my users do not have any connection issues.

Thanks in advance to all answers :-)
0
mercuriousu2
Asked:
mercuriousu2
  • 3
  • 3
1 Solution
 
Jim P.Commented:
If the DB size is less than 10GB you can move it to an Express instance.

The best way is to do a backup and restore to the new instance. There are so many explanations of how to do that, I'll let you do the extended research but it is basically right-click the DB in Management Studio and select backup and follow the prompts. Restore is pretty much a similar idea.

Then use the sp_help_revlogin to transfer logins and passwords between instances of SQL Server.

Now a suggestion to make your life easier in the future. If you have a DB that is on a server, even a named or instance like ServerName1\InstanceName and you have access to your DNS make a CNAme record like MyAppServer that points at the ServerName1. Then in the future if you want to move the DB or instance, all you have to do is modify the CName record to point at ServerName2. You won't have to touch the clients at all.
0
 
David ToddSenior DBACommented:
Hi,

Instead of pushing the database across to the higher-level instance, pull it across from that instance.

Regards
  David
0
 
mercuriousu2Author Commented:
Hi

I tried to restore the database backup to the Express version, I got the error, any ideas?

David: not sure how to achieve that, from the express version the only restore option was browsing locally.


===================================

Restore failed for Server 'ppm-srv-05\SQLEXPRESS'.  (Microsoft.SqlServer.Express.Smo)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&EvtSrc=Microsoft.SqlServer.Management.Smo.ExceptionTemplates.FailedOperationExceptionText&EvtID=Restore+Server&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
   at Microsoft.SqlServer.Management.SqlManagerUI.SqlRestoreDatabaseOptions.RunRestore()

===================================

System.Data.SqlClient.SqlError: Directory lookup for the file "d:\databases\Main1st_Data.MDF" failed with the operating system error 2(error not found). (Microsoft.SqlServer.Express.Smo)

------------------------------
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&ProdVer=9.00.2047.00&LinkId=20476

------------------------------
Program Location:

   at Microsoft.SqlServer.Management.Smo.ExecutionManager.ExecuteNonQueryWithMessage(StringCollection queries, ServerMessageEventHandler dbccMessageHandler, Boolean errorsAsMessages)
   at Microsoft.SqlServer.Management.Smo.BackupRestoreBase.ExecuteSql(Server server, StringCollection queries)
   at Microsoft.SqlServer.Management.Smo.Restore.SqlRestore(Server srv)
SQL-Error.jpg
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Jim P.Commented:
Does the server have a D:\Databases\ folder? You'll probably have to go in and mess with the paths to do the restore.
0
 
mercuriousu2Author Commented:
its not that the restore could not find the .BAK file, I have previously moved it to the default folder it was looking for.
0
 
Jim P.Commented:
The  "d:\databases\Main1st_Data.MDF" is the SQL DB Main Data File that it was trying to write to. So if the folder doesn't exist, or can't be accessed by the SQL Server service it can't do the restore.
0
 
mercuriousu2Author Commented:
Many thanks indeed, this worked fine. Appreciate the response and also the previous DNS tip :-).
0

Featured Post

Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now