不同版本的SQL Server Express [英] Different versions of SQL Server Express

问题描述

我很困惑在我的应用程序中使用什么版本的SQL Express。

我有两个基本要求：



1）应用程序应该在所有操作系统上运行（32位和64位）

2）它应该与Windows Vista及更高版本兼容（Vista，7和8.xxx ）



如果我使用SQLEXPR32_x86_ENU，它会对我有用吗？



请指教。

谢谢

Hi,
I am confused what version of SQL Express to use in my application.
I have two basic requirements:

1) App should run on all operating systems (32 bit and 64 bit)
2) It should be compatible with Windows Vista and above (Vista, 7 and 8.xxx)

If I use SQLEXPR32_x86_ENU, will it work for me?

Please advise.
Thanks

推荐答案

重要的不是你的应用程序，它是SQL运行的服务器，重要的是，有些人会，有些人不会在所有操作系统上运行。您的应用程序通常会在其他PC上运行，只要您安装了所需的.NET框架，就可以了。



例如， SQL Server 2012 SP1不能在Windows 10上运行（根据微软）但SP2会运行。



所以请到这里：安装SQL Server 2016的硬件和软件要求 [ ^ ]并使用其他版本下拉列表检查哪些操作系统兼容。

It isn't your app that matters, it's the server that SQL runs on that matters, and some will and some won't run on all OS's. Your app will generally run on other PCs anyway, and as long as you have the required .NET framework installed on them, you'll be fine.

For example, SQL server 2012 SP1 won't run on Windows 10 (according to microsoft) but SP2 will.

So go here: Hardware and Software Requirements for Installing SQL Server 2016[^] and use the "other versions" dropdown to check which OS's are compatible.

如果如果您在询问与客户端操作系统版本相关的问题，则可能根本不需要SQL Express。在选择支持的数据时要考虑很多事情。

如果您打算在真实的客户端 - 服务器场景中使用DBMS（许多客户端在不同的PC上并行运行数据库服务器引擎），比我的假设错了。



但是我们假设您需要一个独立应用程序的数据库后端。比SQL Server Express可能是一个负担。为什么？因为它是一个成熟的发动机，占地面积很大。当然它有一些你可能真正需要的可重新配置的功能。尽管如此，你无法克服的一件事是安装，因为这也是你的问题。



替代方案称为嵌入式数据库引擎。这些或多或少的库链接您的应用程序，并随您的应用程序一起提供。它们也不作为独立的可执行文件或服务运行。它们将成为您申请的一部分。从SQLite，Firebird Embedded到SQL Server Compact（不是Express！），还有很多其他人都遵守 NoSQL [ ^ ]而不是传统的关系模型。谷歌会建议你很多，我不会。

使用任何类型的嵌入式数据后端时需要考虑的是它们通常不提供任何编程接口，如存储过程。为什么它们会比在应用程序中直接实现相同逻辑的性能更低。请记住，即使在相同的过程中，它们也使用相同的铁。

因此，具有高性能linq接口的优秀嵌入式对象存储器最有可能比独立的rdbms更少地引起独立应用程序的麻烦。

不过，你必须从一开始就考虑到这一点，在规划阶段......

If you are asking questions related to client operating system versions, you might not need SQL Express at all. There are many things to consider in choosing the data backed.
If you intend yo use the DBMS in a real client-server scenario (many clients running in parallel on PCs that are not the same that hosts the database server engine), than I am wrong with my assumption.

But let's suppose that you need a database backend for a stand-alone application. Than SQL Server Express might be a burden. Why? Because it is a full-blown engine, with quite big footprint. Of course it has some remarcable features you might really need. Still, one thing you can not overcome is the installation as this is your problem here too.

The alternatives are called embedded database engines. These are more or less libraries you link your application to, and you ship with your application. They do nor run as standalone executable or service. They will be part of your application. There are many out there from SQLite, Firebird Embedded to SQL Server Compact (not Express!), but also many others that adhere to NoSQL[^] rather than to the traditional relational model. Google will suggest you many, I won't.
What you need to consider when using embedded data backend of any kind is that they usually do not provide any programmatic interface such as stored procedures. Why should they as it would present less performance than implementing the same logic directly in your application. Remember that they run on the same iron and in general even in the same process.
So a good embedded object store with high performance linq interface will most likely cause less headache for a stand-alone application than any rdbms.
Still, you have to consider this right from the start, in the planning phase...

这篇关于不同版本的SQL Server Express的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！