将数据库从 SQL Server 2000 迁移到 SQL Server 2005
将数据库从 SQL Server 2000 迁移到 SQL Server 2005 时可能会遇到哪些技术问题？有什么我应该注意的常见问题吗？
我是否应该担心在针对较新版本的数据库执行存储过程时可能会中断的任何 T-SQL 更改？
DTS 包怎么样？那里有迁移问题吗？
What technical issues am I likely to encounter when migrating a database from SQL Server 2000 to SQL Server 2005? Are there any common problems I should be aware of?
Should i be worried about any T-SQL changes that may break when stored procs are executed against the newer version of the database?
What about DTS packages? Are there any migration issues there?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
一般来说，迁移应该相当简单。
您可以将 SQL 2005 中的数据库设置为在 SQL 2000 的兼容模式下运行，但您不需要这样做。
我建议的一件事是在生产之前先进行测试迁移，只是为了尝试一下并有机会发现任何问题。例如，检查 SQL 2005 中的性能 - 您可能会发现，如果性能下降，某些查询可能需要调整。例如，我见过为了提高 SQL 2000 的性能，查询需要索引提示的实例。这在 SQL 2005 中产生了相反的效果，导致性能更差，这意味着需要再次删除提示（大多数情况下，不需要索引提示）
更新 1：
关于 DTS 包，我不会尝试比 这篇 MSDN 文章 确实如此，它非常全面:)
Generally speaking, migration should be fairly straight forwards.
You can set the database in SQL 2005 to run in compatibility mode for SQL 2000, but you shouldn't have a need for that.
One thing I would advise is to do a test migration first before doing it on production, just to try it out and have the opportunity to catch any issues. For example, check the performance within SQL 2005 - you may find that some queries may need to be tweaked if performance deteriorates. e.g. I've seen instances where to improve performance on SQL 2000, an index hint was required on the query. This had the opposite effect in SQL 2005 resulting in far worse performance, meaning the hints needed to be removed again (as is mostly the case, index hints shouldn't be needed)
Update 1:
Regarding DTS packages, I won't attempt to explain the options better than this MSDN article does, it's pretty comprehensive :)