April 8, 2009 at 9:08 am
I am - at best - a junior DBA. I am still taking classes and learning.
I manage/maintain multiple MS Access front ends that utilize SQL Server back ends. I have three SQL environments for each database: One live and one development on separate network servers, and I have a local instance of the databases on my laptop that I use for development when I am not connected to the network. I have full owner rights on the development and local instances, but not on the live version. I can create/edit tables, views, run queries, and a few other pieces in "live".
I received a request from a test group to move all of the data from the live server to the network development server for testing purposes. I don't need to move it to my local instance.
With my somewhat limited access to the live server and experience level, is there an easy way to move all of that data without having to rebuild the entire database in development? (There's probably a really simple stored procedure, isn't there?...)
Archidrb
April 8, 2009 at 9:12 am
The easiest way is to take your most recent full backup, copy that to the test server, and restore it there. That's assuming, of course, that your databases are being backed up regularly.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
April 8, 2009 at 11:28 am
Backup and Restore is the best way or Import/Export Wizard. Either of them. How many databases have ou got to move?
April 8, 2009 at 12:26 pm
Two databases. I submitted a request internally to have the big one (in '00) moved. I would like to try the import/export, but I am not sure whether I would have that permission in the smaller one. It's a '05 that are more tightly managed.
April 8, 2009 at 12:37 pm
Backup/restore is the simplest way to do this.
The import export is an SSIS package, which essentially scripts out the schemas, runs those on the new server, and then copies data. It's a bunch of things happening and it can fail. Not that it will, but the easiest way is a backup and restore.
April 8, 2009 at 1:24 pm
archidrb (4/8/2009)
Two databases. I submitted a request internally to have the big one (in '00) moved. I would like to try the import/export, but I am not sure whether I would have that permission in the smaller one. It's a '05 that are more tightly managed.
True whatever Steve advised, Since you have only two databases you can backup and restore or what you can do is take the databases offline if your business allows copy the .mdf and .ldf files over to another servers and attach them there.
Viewing 6 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply