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 |
|
frudd
Starting Member
1 Post |
Posted - 2003-11-19 : 21:52:36
|
| Hi everyone, I use SQL 7 (Microsoft SQL Server 7.00 - 7.00.623 (Intel X86) to be exact).Now I want to supply a client with the .bak I have created for them from my SQL Server 7, yet they're on SQL Server 2000.Is this likely to cause any conflictions? Don't know if it's relevant but the only data types I'm using are numeric, int, and nvarchar.In the end I decided to just supply them with the generated SQL script and used DTS to export the db data to excel for them. I just want to know for next time thats all.What about if it was the other way around, with me using SQL Server 2k and giving it to a client on SQL Server 7, obviously now data types would be quite sensitive in this case???thanks for your help and timeRegardsFrudd |
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2003-11-19 : 22:38:02
|
| Restoring a 7.0 backup on a 2000 server is OK. Restoring a 2000 backup on a 7.0 server is not. In the latter case, you might do better to export the data using bcp in native format. It is more compact than using a text format, and you do not have to worry about choosing delimiter characters or quotes, and it handles text, image, and binary columns transparently. The only thing you need to worry about are SQL Server 2000 datatypes like sql_variant and bigint, and whatever new features might be scripted out (INSTEAD OF triggers and CASCADE'ing foreign keys, for example)Books Online has more details on bcp. It's definitely worth checking out and much better than using Excel. |
 |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-11-20 : 12:19:58
|
| When you restore a 7.0 database onto SQL 2000, the upgrade process is done. Just something for you to be aware of. The database compatibility mode is set to 70 so you should be fine.Tara |
 |
|
|
|
|
|
|
|