VistaDB的优点是什么 [英] What are the advantages of VistaDB

问题描述

我已经看到了多年来对VistaDB的引用，以及使用SQLite，Firebird，MS SQL等工具。 et al。我从来没有理由考虑它。

使用另一种技术支付VistaDB vs有什么好处？我想到的事情：

1.紧凑框架支持。 SQLite + MSSQL支持CF。

2.需要迁移路径到一个更鲁棒的系统。 Firebird + MSSQL。

3.需要更多高级功能，如触发器。 Firebird + MSSQL

解决方案

VistaDB客户端运行时是免费的。运行时将永远不会在凌晨3点，因为你把它。只有开发者工具以这种方式获得许可。每个开发人员需要1个许可证，简单。我们甚至提供了一个非常便宜的Lite版本，没有Visual Studio工具。

其他一些优点

100％托管代码 - 引擎中没有互操作或其他非托管调用。这对一些人来说是很大的，其他人不在乎。

VistaDB只是做你所要做的，甚至运行在中信任。

XCopy部署 ）。您可以xcopy您的应用程序，运行时和您的数据库并运行。

隔离存储 - 您需要特殊权限才能在机器上安装或配置可以将整个数据库放入隔离存储并直接从那里运行。这使得非常容易构建安全点击应用程序，以企业环境的域友好的方式写数据库。无需将用户数据存储在共享驱动器上，也不必担心权限映射。

CLR触发器/ CLR程序 CLR代码并将其用作触发器或存储程序。我们刚刚引入了更改，以便更轻松地维护可在VistaDB和SQL Server 2005/2008中运行的单个CLR程序集。

T- SQL Procs - VistaDB T-SQL程序与SQL Server 2005/2008兼容。任何在我们的引擎中工作的过程都将在SQL Server中运行。这并不意味着那里运行的任何东西将移植给我们。我们是SQL Server中的功能的一个子集。但我们也是唯一的方法来运行T-SQL Procs没有SQL Server（SQL CE不能这样做）。

我个人认为最大的功能之一是以后升级到SQL Server的能力。所有VistaDB类型，语法和CLR程序，T-SQL procs等都将在SQL Server上运行。

32/64位部署 - VistaDB是一个运行32位和64位的单一程序集部署，无更改。 SQL CE需要两个不同的运行时，具体取决于操作系统，并且不能在IIS下运行。访问没有64位运行时，最近的32位运行时只能通过MSI部署。

关系完整性 - VistaDB还实际上强制实施您的约束和外部键。您可以进行特定的级联更新和删除操作。评论我们的人就像SQLITE在这方面是错误的。他们解析约束，但不强制它们。

编辑：他们现在支持FK的SQLite。但是它们不是默认编译的，并且不使用与SQL Server相同的语法。

中等信任中等信任Web服务器是许多人不会在乎的另一个功能，但它是一个大问题。许多第三方控件甚至不能在中等信任中运行。

- 完全披露 - 我可以在中信托内部运行完整的引擎，因为我们承诺提供100％的托管代码和最低权限。是VistaDB的所有者，所以我可能有偏见。 ：）

I have seen the references to VistaDB over the years and with tools like SQLite, Firebird, MS SQL et. al. I have never had a reason to consider it.

What are the benefits of paying for VistaDB vs using another technology? Things I have thought of:
1. Compact Framework Support. SQLite+MSSQL support the CF.
2. Need migration path to a 'more robust' system. Firebird+MSSQL.
3. Need more advanced features such as triggers. Firebird+MSSQL

解决方案

The VistaDB client runtime is free. The runtime will never "expire at 3am" as you put it. Only the developer tools are licensed in that manner. You need 1 license per developer, simple. We even offer a really inexpensive Lite version with no Visual Studio tools.

Some other benefits

100% managed code - there are no interop or other unmanaged calls in the engine. This is a big deal to some, and others couldn't care less.

No registry access required - Most other in proc databases require registry access to look for parent controls, or permissions. VistaDB only does what you tell it to do, and will even run in Medium Trust.

XCopy deployment for runtime and your database (single file). You can xcopy you application, the runtime, and your database and run. Nothing to install or configure on the machine, no special privileges needed (we can run in Medium Trust or higher).

Isolated storage - You can put your entire database into Isolated Storage and run it from there directly. This makes it very easy to build secure click once applications that write databases in a domain friendly way for corporate environments. There is no need to store the user data on a shared drive or worry about permission mapping.

CLR Triggers / CLR Procs - You can write CLR Code and use them as Triggers or Stored Procs. We have just recently introduced changes to make it even easier to maintain a single CLR Assembly that can run in both VistaDB and SQL Server 2005/2008.

T-SQL Procs - VistaDB T-SQL Procs are compatible with SQL Server 2005/2008. Any procedure that works in our engine will run in SQL Server. That does not mean anything that runs there will port to us. We are a subset of the functionality in SQL Server. But we are also the only way to run T-SQL Procs without SQL Server (SQL CE can't do it).

I personally think one of the biggest features is the ability to upsize to SQL Server later. All of the VistaDB types, syntax, and CLR Procs, T-SQL procs, etc all will run on SQL Server. (You can't take everything from SQL Server down to VistaDB though, it is a subset)

32/64 bit Deployment - VistaDB is a single assembly deployment that runs both 32 and 64 bit without changes. SQL CE requires two different runtimes depending upon the OS, and cannot run under IIS at all. Access has no 64 bit runtime, and the most recent 32 bit runtime can only be deployed through MSI. The 32 bit version of Windows has the runtime, the 64 bit version does not.

Relational Integrity - VistaDB also actually enforces your constraints and Foreign Keys. You can specific cascade update, and delete operations. The person who commented we are like SQLITE is wrong in this regard. They parse constraints, but do not enforce them.

EDIT: They do have support for FK's now in SQLite. But they are not compiled in by default, and do not use the same syntax as SQL Server.

Medium Trust - The ability to run on a medium trust web server is another feature that many will not care about, but it is a big deal. Many third party controls can't even run in Medium Trust. We can run the complete engine within Medium Trust because of our commitment to 100% managed code and least permission required.

- Full disclosure - I am the owner of VistaDB so I may be biased. :)

这篇关于VistaDB的优点是什么的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！