|
SQL Server 2000桌面引擎(MSDE 2000) |
||||
|
|
||||
|
|
||||
|
|
||||
|
||||
|
|
|
|
产品概述 SQL Server 2000桌面引擎是一个基于SQL Server核心技术构建的软件数据引擎。MSDE 2000具备针对单处理器和双处理器的支持特性,是企业应用程序桌面扩展的可靠存储引擎和查询处理器。由SQL Server与MSDE 2000所共享的通用技术可确保广大开发人员创建出能够以无缝化方式从便携计算机扩展至多处理器群集的应用程序。 由于MSDE 2000被设计为以后台方式运行,因而,无需配备自身特有的用户界面(UI)或软件工具,并可针对事务处理桌面应用程序提供相关支持。广大用户可借助嵌有MSDE 2000的应用程序与该引擎进行交互操作。为便于单独销售或嵌入其它产品,MSDE 2000通常被封装成自解压文件形式。 您还可将MSDE 2000内建于某一借助Microsoft开发工具(如Microsoft Visual Studio®和Microsoft Office开发人员版)创建、并且无需支付特许权使用费的应用程序。这种方式将允许开发人员营造出企业级可靠性,并将数据库功能特性扩展至桌面应用程序。 便携性与兼容性 与SQL Server全面兼容的MSDE 2000是一种无需支付特许权使用费、并可供再次销售的数据库引擎。MSDE 2000的设计意图体现为,以嵌入数据库方式基于Microsoft Windows® 98、Windows千禧版(Windows Me)、Microsoft Windows NT® Workstation 4.0版(配备Service Pack 5或更高版本)或Windows 2000 Professional系统平台运行,并在此基础上针对需要使用本地数据库引擎的定制应用程序提供支持。 与使用Microsoft Jet数据库相比,选配MSDE 2000无疑具有更加难以抗拒的吸引力。MSDE 2000的设计目标首先是,面向那些需要能以简便快捷方式随同增值商务解决方案一并销售和安装之数据库服务器的开发商提供一种成本低廉的软件选择。由于MSDE 2000可与SQL Server的其它版本实现全面兼容,因此,广大开发人员能够轻而易举地将SQL Server和MSDE 2000一并定位于完全相同的核心代码基础。而这就在应用程序超越MSDE 2000存储与扩展极限的情况下,提供了一条从MSDE 2000到SQL Server的无缝化升级途径。 产品获取方式 下表中所列示的Microsoft应用程序全部包含有MSDE 2000,并需要对该产品所具备的数据管理与存储服务加以应用。
您可借助下表中所列示的Microsoft应用程序创建令MSDE 2000充当数据存储的应用程序。每种产品的最终用户许可协议(EULA)均已就再销售权限和相关指导原则加以明确界定。
产品定价政策 针对MSDE 2000许可授权的处理方式将取决于其所随同销售的产品。 § Office XP专业版与Visio 2000:Office XP及Visio 2000许可授权用户将被授予一份针对单一用户的MSDE 2000许可授权。 § Office XP开发人员版与MSDN Universal Subscription:在MSDE 2000基础上建立应用程序的开发人员将有权根据EULA中所制定的相应条款随同Office XP开发人员版与MSDN Universal Subscription一起免费销售MSDE 2000。 § SQL Server:对于每一种与SQL Server 6.5、SQL Server 7.0或SQL Server 2000数据库进行连接或将其作为数据源加以访问的MSDE 2000部署方案来说,均必须单独购买适当的许可授权,在这种情况下,既可为每台MSDE 2000设备购买一份SQL Server CAL,也可为MSDE 2000所依赖的后端SQL Server服务器购买SQL Server处理器许可授权。 技术支持 MSDE 2000软件服务包将作为SQL Server软件服务包的组成部分之一与其同时提供。如欲下载最新发布的SQL Server软件服务包,请访问Microsoft下载中心。 此外,您也可以通过Microsoft主要技术支持联系人来获取软件服务包。如需获取更多关于Microsoft产品支持服务(PSS)的信息,请访问Microsoft PSS Web站点。 所支持的语种 MSDE 2000针对以下语种实现了本地化处理: § 简体中文 § 繁体中文 § 法语 § 德语 § 意大利语 § 日语 § 朝鲜语 § 西班牙语 特性与功能 MSDE 2000将通过提供以下特性的方式帮助您建立定制化解决方案。 多实例支持能力。MSDE 2000最多可在单台计算机上同时支持16个数据库服务器实例。 Osql.exe。osql实用工具是Microsoft所提供的一种用于临时以交互方式执行Transact-SQL语句或脚本程序的Win32命令行工具。借助这种实用工具,您将可以在一种类似于命令提示行的工作环境中以交互式方式输入Transact-SQL语句。相应语句所生成的结果集也将在命令行窗口中加以显示。 复制功能。MSDE 2000同时支持以发布者及订阅者身份所进行的合并复制操作,从而使您得以在多个站点(某些情况下可能会覆盖数以百计的站点)上同时维护相同数据的多份拷贝。此外,MSDE 2000还支持其它形式的复制操作,但其只能提供范围有限的功能。例如,MSDE 2000只能在订阅者环境中参与事务化复制和快照复制操作。 如需获取更多关于SQL Server复制功能的信息,请访问MSDN Library。 性能。MSDE 2000是一种可共享的本地化数据引擎。它拥有一种能够为达到性能优化目的而将最大并行批处理工作负载数量控制在5个以内的可管理并行工作负载控制机制。相关命令与日志记录可对实例进行监控,以避免出现并行执行工作负载数量超过5个的情况,在这种情况下,即便是配置良好的系统,也会产生明显的性能下降。当并行执行的工作负载数量超过5个时,如果再有批处理工作负载被提交上来,并行控制机制将不断减慢系统运行速度。这些工作负载既不会被取消,也不会自己丢失;他们仍将在一种不断下降的性能模式中得到处理。如果您的解决方案必须支持5个以上的并行工作负载,那么,我们强烈建议您移植到SQL Server 2000或SQL Server 2000企业版,以便获得具备更高伸缩能力的最佳优化性能。 最大数据库规模。MSDE 2000最多可为每个数据库提供2 GB存储空间。这一限制条件是以数据库而非服务器为单位的。每台计算机可支持多个MSDE 2000实例,其中每个实例为数据库所提供的存储空间之和不得超过2 GB。 数据转换服务。MSDE 2000有能力运行数据转换服务(DTS)软件包。然而,由于其并未配备相应的DTS设计器,因此,它将无法设计DTS软件包。 远程管理功能。MSDE 2000同时支持本地管理与远程管理方式。然而,由于相关事务可能在不同服务器之间交替产生,因此,MSDE 2000将无法在多服务器运行环境中实现远程管理。 有关Windows 98的限制条件。Windows 98将无法提供针对以下特性的支持能力: § Windows NT身份验证机制 § 纤维模式调度 § 异步I/O方式 § 预读取机制 § 性能监视器计数器 § 分散/聚集I/O方式 § 名称管道服务器网络支持库 § Appletalk服务器或客户端网络支持库 § Banyan Vines服务器网络支持库 系统需求 如欲运行MSDE 2000,您的系统必须首先满足以下所列出的最低需求条件: § 配备166-MHz或更高频率奔腾处理器的计算机。 § Windows 98、Windows Me、配备Service Pack 5或更高版本软件服务包的Windows NT Workstation 4.0、配备Service Pack 5或更高版本软件服务包的Windows NT Server 4.0、配备Service Pack 5或更高版本软件服务包的Windows NT version 4.0 Server企业版、Windows 2000 Professional、Windows 2000 Server、Windows 2000 Advanced Server或者Windows 2000 Datacenter Server操作系统。 § 至少32兆(MB)RAM内存容量。(建议配置64 MB或更高内存容量,根据具体操作系统需求,可能需要提供更多内存容量。) § 44 MB可用硬盘空间 如需获取更多相关信息 请访问将MSDE与您的应用程序加以集成页面。 |
将MSDE 2000 Setup嵌入到自定义应用程序安装中
![]()
|
|
|
||||||||||
|
|
|
|
|||||||||
|
|
|
|
摘要
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000,Microsoft SQL Server桌面引擎)使得开发人员能够将数据存储嵌入到他们的自定义应用程序中。MSDE 2000技术提供了与 SQL Server兼容的本地数据存储。本文包含了关于如何通过在自定义应用程序的安装程序内嵌入MSDE 2000 Setup,使用自定义应用程序发布MSDE 2000的信息。
文中包括:
§ 引言
§ Windows Installer和合并模块
§ 创建MSI包
§ 进行成功合并操作的必要条件
§ 合并技术
§ 运行安装程序
Integrating MSDE 2000 with your Applications |
||||
|
|
||||
|
|
||||
|
|
||||
|
||||
|
|
|
|
|
The SQL Server 2000 Desktop Engine (MSDE 2000) offers application developers new opportunities to build desktop and shared solutions that are freely distributable and can be easily migrated to SQL Server 2000 technology if the customer or end-user wants to scale the solution up to thousands of users or terabytes of data. For example: § Developers can offer an introductory or trial edition of their full product that ordinarily ships with SQL Server 2000. § Developers can point to a full range of scalability in their products, where no upgrade or conversion is required if the customer wants to scale the application to serve the entire enterprise. § Corporate developers can fully leverage their investment in software development; assuring that applications initially intended to serve the desktop or a small department can be leveraged across the entire enterprise if needed, without requiring a change to single line of code. LicensingDevelopers can freely distribute MSDE 2000 solutions built with SQL Server 2000 Developer Edition, Microsoft Visual Studio® .NET development tools, or with Microsoft Office 2000 Developer edition. See the End-User License Agreement (EULA) for the full redistribution and royalty terms. Methods of DistributionWith MSDE 2000, application developers are given the ability to install a redistributable relational database engine, fully compatible with SQL Server 2000 as part of the custom application setup process. Application solutions using MSDE 2000 can store data in a desktop engine whose configuration and resources are managed dynamically, removing the need for extra graphical tools and administrative utilities. This makes MSDE 2000 the ideal database to embed into desktop and laptop applications. There are two ways application developers can build the MSDE 2000 installation into their application setup. After the database engine is installed, developers can use standard SQL Server APIs to build and manage database objects. Using MSDE 2000 with Windows InstallerUsing Windows Installer technology, MSDE 2000 is shipped as a set of Windows Installer merge modules. The application developer uses these merge modules to install an instance of MSDE 2000 during the customized application setup. This is done by either integrating the merge modules into a standard Windows Installer setup procedure, or having the custom application setup program call Windows Installer directly to an instance of MSDE 2000. The embedded database engine footprint can be reduced by excluding specific feature merge modules (like replication, Distributed Management Objects, and so forth) which the application may not use. To learn more how to integrate MSDE 2000 into applications using Windows Installer technology, read Using SQL Server Desktop Engine Merge Modules on the MSDN® site. Setting Up MSDE 2000 Using Non-Windows Installer ProgramsTo set up an MSDE 2000 instance for an application using programs other than Windows Installer, MSDE 2000 provides a Setup.exe utility file. This file opens up a shell that calls Windows Installer to install an instance of MSDE 2000. You can define settings for customizing the way Setup.exe installs MSDE 2000. These settings can be specified through either command prompt switches or an .ini file. Together with the Setup.exe utility, you will have to distribute the 16 MSDE 2000 installer packages (SQLRun##.msi). Each installer package is a unique MSDE 2000 instance. Before attempting to install an instance of MSDE 2000, an application setup process should first ensure that the proposed instance name has not already been used by another instance of SQL Server, and the computer does not already have more than 16 instances (or 15 named instances) installed. Otherwise, a globally unique identifier (GUID) clash may occur. SQL Server 2000 supplies two API functions to perform these checks. For more information on how to manage the distribution of MSDE 2000 installer files, read Managing Desktop Engine Installation Package Files on MSDN. The setup utility will also check if Windows Installer is installed on the target computer. If Windows Installer is not found, the setup utility will try to install it. The setup utility will then proceed to select an unused MSDE 2000 installer package for this particular installation. This is important if your application supports multiple instances of MSDE 2000. Installing MSDE 2000 without creating your own Windows Installer package can increase the risk of a GUID clash. If your application does not support multiple instances of MSDE 2000, and you are sure that no other identical MSDE 2000 instance will be installed on the target computer, you can distribute a cloned or created Windows Installer package with a GUID, and pass this Windows Installer Package file name when calling the Msiexec.exe utility. In this case, you will not need to distribute all 16 MSDE 2000 installer packages. To learn more on how to use the Setup.exe utility of MSDE 2000, read Customizing Desktop Engine Setup.exe on MSDN. Manually Setting Up an MSDE 2000 Database InstanceApplications that do not use Windows Installer–based setup programs can also install an instance of MSDE 2000 by calling Windows Installer directly. This is done by calling Msiexec.exe directly. This is typically done when the application setup program has a DLL available that contains a Windows Installer callback function that can process the return codes generated by the MSDE 2000 Windows Installer merge modules. To see a sample installation procedure, read Desktop Engine Installation Samples on MSDN. Integrating MSDE 2000 with Office ApplicationsMSDE 2000 is not automatically installed during the Microsoft Office XP installation. The installation files are on the Office XP CD, in the \MSDE2000 folder. Start the installation by running Setup.exe. After you have installed MSDE 2000 on your computer, if you are running Microsoft Windows® 98 or later, you may need to start the SQL Server Service Manager (double-click the MSSQLServer icon on the taskbar and click Start/Continue). MSDE 2000 starts automatically on computers running Microsoft Windows NT® 4.0 or later. You might want to automatically start MSDE 2000 on Windows 98 or later by selecting the Auto-start service when OS starts check box on the SQL Server Service Manager window. |