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 |
|
ej
Starting Member
2 Posts |
 Posted - 2004-05-04 : 21:56:41
|
| I have just had a sql server 2000 db dropped in my lap! I am new to sql, though not new to relational databases.My first task is to copy the database, which houses a small shopping cart, from the old host to a new host, to create a testing environment. Once that is complete, I'll need to copy the whole thing again to a production environment. I was wondering if the backup and restore feature of the Enterprise Manager is the way to go on this -- I want to be sure I get everything relevant, such as triggers, functions, scripts.I did a search and found some good info, such as tduggan's isp_transfer_logins code, but feel free to point me in the direction of any other existing info on the topic. Any assistance will be met with heartfelt appreciation!! EJ |
|
|
derrickleggett
Pointy Haired Yak DBA
4184 Posts |
Posted - 2004-05-04 : 22:09:31
|
| I prefer to do it that way. After the restore, I run a script like Tara's to set up the users. If you run it after the restores are done, it will be able to set the default dbs intact and avoid user "issues". :)MeanOldDBAderrickleggett@hotmail.comWhen life gives you a lemon, fire the DBA. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-05 : 13:07:07
|
| The backup and restore will grab everything except users, jobs, DTS packages, and other stuff that are stored in the system databases. Users are stored in master. My code will transfer those. jobs and DTS packages are in msdb database. Here's a great article about moving databases:http://support.microsoft.com/default.aspx?scid=kb;en-us;314546Tara |
|
|
|
ej
Starting Member
2 Posts |
Posted - 2004-05-05 : 22:07:16
|
Thanks so much y'all! That is really useful info for me. I'm so relieved that you didn't say, "What are you crazy, you'll never figure this out!!"  EJ |
|
|
|
damon417
Starting Member
1 Post |
Posted - 2004-05-18 : 09:24:51
|
| I am new to sql as well but not relational databases. I am a new hire and the company is using sql server 7.0. Anyhow, before I find thousands of reference materials my main question revolves around copying over the DB to my local machine and running our M.S. Access based front end to manipulate the DB. We have a nutritional program that came with it's own sql server engine which is currently on my machine. Therefore, I ran the export function from sql server and copied all the tables, not sure about any of the other functions, over to the sql server on my local machine. The Access based program is one that we copy to all the local machines and create an ODBC connection over to the server. Logically I re-configured the ODBC connection to point to the sql server on my machine and not the server's. The problem is that when I create dummy info in the access portion, it gets created in the DB on the server as well. So I'm currently trying to figure out how to move the data and isolate it on my machine so I don't frag the info on the server. Any advice would be appreciated and I'll be around this site most of the day looking at postings and trying to learn sql server.Thanks,D. Gray |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2004-05-18 : 12:24:39
|
| Use BACKUP/RESTORE to get the database onto your machine. Then fix the logins. Then modify the connection string to point to your machine.Tara |
|
|
|
|
|
|
|
|
new to sql - copying a sql db