将 SQL Server 2000 从 x86 升级到 x64？
我有一个当前为 x86 的 SQL Server，我想将其升级到 x64。 它在 x64 版本的 Windows 上运行，我认为这就像配置服务器时安装了错误的版本一样简单。 这是一个生产服务器，所以我最关心的是保持登录名不变，因为每个用户都有自己的 SQL 登录名。 我做了一些搜索，发现 专家交流线程给出了以下步骤，但他从未报告过它是否有效。
- 分离数据库 - 所有用户数据库、模型和 msdb。
- 脚本登录 (http://support.microsoft.com/kb/918992/) 和作业
- 保存数据库文件和脚本
- 卸载 SQL
- 安装 sql x64
- 附加数据库
- 一旦文件位于正确位置，就重新附加数据库。
- 如果未重新连接 msdb，则运行登录和作业脚本。
除了您不需要将系统数据库传输到新实例（因此步骤 1 不太正确，除了编写任何特殊 XP 或您创建的其他任何内容的脚本之外）之外，任何人都可以想到其他任何方法吗？那需要做什么？ 更重要的是，有人真正尝试过吗？ 你能分享一些故事或陷阱吗？或者进展顺利吗？
I have a SQL Server that's currently x86, and I'd like to upgrade it to x64. It's running on an x64 version of Windows, and I think it's as simple as the wrong version having been installed when the server was configured. It's a production server, so my biggest concern is getting the logins over unaltered, since every user has their own SQL login. I've done some searching, and found an Experts-Exchange thread that gave the following steps, though he never reported back if it worked.
- detach databases - alluser dbs, model and msdb.
- script logins (http://support.microsoft.com/kb/918992/) and jobs
- save db files and scripts
- unintall SQL
- install sql x64
- attach dbs
- re attached dbs once files are in correct place.
- run scripts for logins and jobs if msdb is not reattached.
Aside from the fact that you don't need to transfer the system databases to the new instance (so step 1 isn't quite correct, aside from scripting any special XPs or anything else you've created), can anybody think of anything else that needs to be done? More importantly, has anybody actually tried this? Can you share any stories or gotchas, or did it go smoothly?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
我做到了，但并不好玩。 有一些问题领域。
I did it and it was not fun. There were a few problem areas.
我已经在 SQL Server 2005 和 2008 上执行过多次 - 据我所知没有任何问题。 因此，根据我的经验，只要您没有任何旧的东西（例如可能依赖于 32 位与 64 位的扩展存储过程），我就不会遇到任何麻烦。 数据库部分应该没问题。
Marc
Follow-up：参考另一个答案 - 我没有 SQL Mail 也没有大量的 DTS 软件包需要升级，所以我无法对它们发表评论。
I've done it several times on SQL Server 2005 and 2008 - without any problems as far as I can tell. So based on my experience, I wouldn't expect any troubles as long as you don't have any old things like extended stored procs that might be dependant on 32- vs. 64-bits. The database parts should be just fine.
Marc
Follow-up: referring to the other answer - I didn't have either SQL Mail nor large amounts of DTS packages to upgrade, so I cannot comment on those.