| Author |
Topic |
|
faroukyew
Starting Member
3 Posts |
 Posted - 2006-10-18 : 02:18:47
|
| Hi all,We do our development in SQLServer 2005. We want to backup and restore our database into the client's side who use SQLServer 2000. Backup and restore cannot work. We try to script the database in 2005 and change the option script to 2000. This fails also. What other option I can use?Regards |
|
|
Merkin
Funky Drop Bear Fearing SQL Dude!
4970 Posts |
Posted - 2006-10-18 : 03:31:06
|
| Get your client to upgrade ?Or develop using the same environment you intend to deploy to.Run your table create scripts and stored proc scripts against your client site, then copy data.Damian"A foolish consistency is the hobgoblin of little minds." - Emerson |
 |
|
|
faroukyew
Starting Member
3 Posts |
Posted - 2006-10-18 : 22:02:35
|
Hi,Thanks for the reply. I wish I can but a lot of red tape to convince them to upgrade and time needed to do so. I am just surprised that this cannot be done easily. MS should consider the backward compatibility so we developers do not loose the biz opportunities for clients who have not upgrade. It will be disadvantageous to developers to maintain 2 version of databases in 2000 and 2005.Anyone?Regards.quote:
Originally posted by Merkin
Get your client to upgrade ?Or develop using the same environment you intend to deploy to.Run your table create scripts and stored proc scripts against your client site, then copy data.Damian"A foolish consistency is the hobgoblin of little minds." - Emerson
|
|
|
|
byrmol
Shed Building SQL Farmer
1591 Posts |
Posted - 2006-10-18 : 22:08:16
|
quote:
MS should consider the backward compatibility so we developers do not loose the biz opportunities for clients who have not upgrade.
They do have backward compatibility. A 2000 db works on 2005You are after forward compatibility. A 2005 db works on 2000Not going to happen...Suck it up and have 2 dev environments..DavidMProduction is just another testing cycle |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-10-18 : 22:11:44
|
quote:
Originally posted by faroukyew
Hi,Thanks for the reply. I wish I can but a lot of red tape to convince them to upgrade and time needed to do so. I am just surprised that this cannot be done easily. MS should consider the backward compatibility so we developers do not loose the biz opportunities for clients who have not upgrade. It will be disadvantageous to developers to maintain 2 version of databases in 2000 and 2005.Anyone?Regards.
If you want to be able to sell your product on SQL 2000 and SQL 2005, it is up to you to maintain the code base for both platforms.There is no point complaining about Microsoft. It's your product, not theirs.CODO ERGO SUM |
|
|
|
faroukyew
Starting Member
3 Posts |
Posted - 2006-10-19 : 00:12:48
|
Thanks for all the replies and opinions. Just a question, on the SQLServer2005, I can script backwards to SQLServer 2K but I tried and it does not work. Anyone done that b4?Is there any solution, freeware, shareware or 3rd party solution to this? Maintaining 2 versions will be exhaustive on our end... Thanks.Regards.quote:
Originally posted by Michael Valentine Jones
quote:
Originally posted by faroukyew
Hi,Thanks for the reply. I wish I can but a lot of red tape to convince them to upgrade and time needed to do so. I am just surprised that this cannot be done easily. MS should consider the backward compatibility so we developers do not loose the biz opportunities for clients who have not upgrade. It will be disadvantageous to developers to maintain 2 version of databases in 2000 and 2005.Anyone?Regards.
If you want to be able to sell your product on SQL 2000 and SQL 2005, it is up to you to maintain the code base for both platforms.There is no point complaining about Microsoft. It's your product, not theirs.CODO ERGO SUM
|
|
|
|
robvolk
Most Valuable Yak
15732 Posts |
Posted - 2006-10-19 : 00:41:55
|
| Well, it might worth asking if you have any other clients, more important than this one, who require SQL 2005. If you don't have a business avenue for 2005, why do you need to develop in it? You're right that it will be exhausting to maintain 2 dev environments, perhaps you shouldn't try. There's nothing in a 2000 version that won't work in 2005, unless you're working with deep hacks or undocumented stuff. |
|
|
|
khtan
In (Som, Ni, Yak)
17689 Posts |
Posted - 2006-10-19 : 01:41:23
|
Just develop on 2000 and deploy to 2000 or 2005 depending on customer's requirement
KH |
|
|
|
jezemine
Master Smack Fu Yak Hacker
2886 Posts |
Posted - 2006-10-19 : 01:44:34
|
quote:
Originally posted by faroukyewThanks for all the replies and opinions. Just a question, on the SQLServer2005, I can script backwards to SQLServer 2K but I tried and it does not work. Anyone done that b4?
Did you do this on a db with the compatibility level set to 80? If not try that.SqlSpec - a fast, cheap, and comprehensive data dictionary generator for SQL Server 2000 and 2005 - http://www.elsasoft.org |
|
|
|
|
SQLServer 2005 and 2000