Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
techno tim
Starting Member
2 Posts |
 Posted - 2006-11-21 : 12:12:25
|
| We are running SQL 2000 as the backend database for an application. We have 5 database's that represent diffirent companies. We want to copy one of these company databases so that we have a test company database that we can run some new procdure on it to see if they work before trying on the live company database.I got some instruction from the application software company on how to copy the database and set it up as a test compnay but the copying part of the database fails. I use the DTS Import\Export wizard and select the company database to copy and give it a new name, I go through another couple of windows then it present me with the summary window on which I click Finish. A new window opens (Executing package) it goes through to 100% then restarts again from 0% it gets to around 22% then fails, I get a small window pop up say "Failed to copy objects from Microsoft SQL server to Microsoft server" and thats it.The application company were of little help so can anybody explain to me how I can find out what the problem is please. Couple of other points, I did this at a time when no users were logged on and the SQL server was running, I log on to the SQL server as domain administrator on the sql server.Has anybody any suggestions?? (in plain non techno speak if possible)RegardsTim |
|
|
Kristen
Test
22859 Posts |
|
|
techno tim
Starting Member
2 Posts |
Posted - 2006-11-22 : 08:46:09
|
| Going to show my total lack of knowledge here.I assume you are referring to SQL own back-up system as opposed to a backup like veritas??We certainly do want all the data as the copied database has to act like the real one so we can test some new procedure on it before we commit to the live database.I had a look at the link you posted and although there is not doubt a lot of useful information there I could not see anything specfic to what I am wanting to to (can't see the wood for the tress??)Any chance of a line by line howto or am I asking to much??Tim |
 |
|
|
Kristen
Test
22859 Posts |
Posted - 2006-11-22 : 09:03:07
|
| You are either:1) backing up from the database direct from the database to tape2) making a SQL Server backup file, and then backing that file up to tape3) God Forbid! backing up the physical SQL Server files .MDF and .LDFCan't help you with (1) unless you can restore from tape to a normal .BAK file on disk, and then proceed as (2). But presumably you can restore direct from tape to a NEW DATABASE - rather than overwriting the original one? If so this would do the trick.(2) As per my link, you need to use the RESTORE command in SQL server to restore from a backup file on disk (that was made with SQL's BACKUP command). A Backup file contains everything about the database - Structure, Data, Users, Permissions. However, the physical logins for a user are stored Server-wide, rather than database-specific, so if you restore to a DIFFERENT Server you will need to perform an extra step to synchronise the User information in the database with the server-wide User Login details. (But I think you are wanting to restore to a newly-named database on the SAME server, in which case none of that applies,a nd you'll be fine)(3) Change you backup policy! but you can restore the files to a separate folder, rename them, move the renamed-files to the SQL Server data folder, and then ATTACH the newly named database.Ask for clarification on anything you need help with.Kristen |
|
|
|
|
|
|
|
|
Copy database failure