问题描述

我有一个应用程序当前正在运行一个 32 位 SQL Server 2005 标准版数据库.由于我不会在这里讨论的原因，我需要将数据库移动到在 64 位 Windows Server 2003 R2 数据中心上运行的 64 位 SQL Server 2005 标准版.

I have an application that is currently running against a 32-bit SQL Server 2005 Standard Edition database. For reasons I won't go into here, I need to move the database to a 64-bit SQL Server 2005 Standard edition running on 64-Bit Windows Server 2003 R2 Datacenter.

在应用程序代码、存储过程或 SQL 配置中是否有任何我应该注意的迁移问题?也就是说，两个平台上的功能是否相同?

Are there any migration issues I should be aware of in the Application code, stored procedures, or SQL configuration? That is, is the functionality equivalent on both platforms?

如果存在功能差异，您能否发布包含迁移计划提示的文档链接?

If there are functional differences, could you post a link to a document with migration planning tips?

推荐答案

总的来说，这是小菜一碟.我们一直都在做这件事，没有任何问题.纯 t-sql 代码的功能是相同的(64 位只是性能更好;-).

In general, it's a piece of cake. We do that exact thing all of the time, with no problems. Functionality of pure t-sql code is identical (64 bit just performs better ;-).

我遇到的一个例外是扩展存储过程.由于这些是用 C 编写的，因此必须将它们重新编译为 64 位二进制文​​件.即便如此，也不需要更改源代码.

The one exception to this that I have encountered is extended stored procedures. Since these are written in C they would have to be recompiled as 64 bit binaries. Even then, no source code changes should be required.

如果您不使用扩展存储过程，您应该没有问题.

If you aren't using extended stored procs you should have no problems.

这篇关于SQL Server 应用程序在 32 位和 64 位版本的 SQL Server 之间的可移植性?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持编程学习网！