December 11, 2012 at 11:18 am
If you haven't read my posts before, I'll introduce myself: I'm a botanist by training but I got roped into managing our database, so I can figure some stuff out on my own, but I need help for more complicated tasks. I've been tasked (because no one is going to do it for us) with migrating our database from one server to the other. I'm posting this forum topic because I was hoping for advice and guidance in making sure this happens more or less smoothly.
Our current databases use Access as a front-end product for data entry/analysis but we store the data on SQL Server tables (because we have a multi-user environment and we allow users to query our data from the web). We two servers (tulip and panda) for our work. Tulip is the server running SQL Server (version 2000) and where we keep the SQL Server tables. Panda is where we keep the Access databases.
We have the opportunity to migrate our databases to a new server (running up to date software) and I have some questions, as I assume that moving the databases is more involved than just cutting and pasting.
Is there anything I need to watch our for when making the migration?
Is there any need (I can't think of any from my end) to keep the Access and SQL Databases on separate servers?
As far as I know our current server is not part of a domain (sorry if I butcher terminology) but it will be on the new server. Will that cause problems?
Any other guidance/advice you could offer would be great. I intend to back up the current databases and run lots of tests before committing to the migration and I also intend to read up on my own as much as possible so that I'm well-informed.
December 11, 2012 at 11:09 pm
you are migrating database to which version?
You planning for in-place or side by side up-gradation ?
Just keep in mind few steps
Run upgrade adviser to check for incompatibility for application/database server while upgrading.
if any warnings/errors found ,solve it before migrating database
if you are planning side by side migration follow below steps
ON current server
1)Backup your all databases (Including system databases)
2)script out your SQL server Jobs
3)take out Transfer logins script
http://blog.netnerds.net/2009/01/migratetransfer-sql-server-2008200520007-logins-to-sql-server-2008/
ON New server
4)Restore all USER databases from backups
5)run all the job scripts you got in 2nd steps above
5)Copy the output of the script provided in step 3 above and run it on new server
-----------------------------------------------------------------------------
संकेत कोकणे
December 12, 2012 at 3:59 pm
>>Is there any need (I can't think of any from my end) to keep the Access and SQL Databases on separate servers?
Best practice is not to put anything on a SQL Server besides SQL Server. In a small environment like yours this may not be possible.
I would definitely not install Access on the SQL Server. It would probably be OK to place the Access mdb files on the server, so the server is essentially acting as a network file share.
December 14, 2012 at 5:36 am
hi,
please check no of linked server .
also you should keep output of sp_configure before migrating to new server.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply