moebius-for-sql-server安装部署手册

合集下载

sql server安装教程

sql server安装教程SQL Server是一款由Microsoft开发的关系型数据库管理系统。

下面是安装SQL Server的详细步骤：1. 下载SQL Server安装程序：进入Microsoft官方网站，点击下载SQL Server的链接。

选择适合你操作系统版本的安装程序，并保存到本地。

2. 运行安装程序：找到保存的安装程序文件，并双击运行。

安装程序将提供一些选项供你选择，如默认安装路径、安装类型等。

根据自己的需要进行选择，并点击“下一步”继续。

3. 安装规则检测：安装程序将自动进行系统检测和验证，确保系统满足安装要求。

如果出现任何错误或警告信息，请根据指示解决问题，并点击“重新运行”以重新进行检测。

4. 接受许可协议：阅读并接受许可协议条款，然后点击“下一步”。

5. 选择安装类型：根据自己的需求选择安装类型。

常见的安装类型包括默认安装、自定义安装等。

如果你不熟悉SQL Server 的各个组件和功能，请选择默认安装以获得最常用的功能。

6. 选择安装功能：根据自己的需求选择安装需要的功能。

如果你是开发者或数据库管理员，建议选中包括数据库引擎、管理工具等在内的所有功能。

7. 设置实例：创建新的数据库实例或选择现有的数据库实例。

数据库实例是SQL Server中的一个独立的数据库环境，可以包含多个数据库。

8. 配置服务器：根据需要配置SQL Server的服务器设置，包括实例名称、身份验证模式、管理员账户等。

9. 配置服务账户：选择用于运行SQL Server服务的用户账户。

可以选择使用系统账户，或者手动输入账户信息。

10. 确定安装位置：确认安装的位置和空间要求，并选择数据文件和日志文件的默认路径。

11. 配置权限：选择默认或手动配置权限，以控制访问SQL Server的用户和角色。

12. 准备安装：确认安装设置和配置，并点击“安装”按钮开始安装。

13. 安装过程：安装程序将自动完成剩下的安装过程，包括文件复制、注册表设置等。

AIMS SQL Server安装指南说明书

Document Version: 4.3 March 2020CONTENTSAIMS Installation Guide (3)Installing the AIMS Software (4)Pre-Requisites (4)Installation (4)Shortcuts (4)Directory Structure (5)Microsoft SQL Server configuration (6)Windows Authentication (13)Configuring the client workstations to connect to AIMS (16)Troubleshooting AIMS SQL Server installation (17)Opening AIMS and entering the license keys (20)AIMS Installation GuideThe SQL Server version of AIMS requires the installation of Microsoft SQL Server 2000, 2005, 2008, 2012 or 2014. The SQL Server version will be more stable than AIMS Access in a networked environment with heavy usage (more than 15 users needing access to the database at the same time), and / or where AIMS needs to be accessed over a Wide Area Network (e.g. from other offices).PLEASE READ THE CONFIGURATION GUIDE CAREFULLY AFTER YOUINSTALL THE SOFTWAREAIMS isa complex case management database. To make best use of it, there are several configuration issues to consider before you start entering data.Make sure you use the AIMS installer shown on your licence certificate. The licence number on the certificate will not activate any otherversion of the software.Supported NetworksAIMS requires an “always on” network connection,and for this reason, peer-to-peer, wireless, orany other network setup that provides onlyintermittent connectivity is not supported.The AIMS Team do not provide support for anytechnical issues relating to networking, we areonly able to provide support for AIMS users intheir day-to-day usage of AIMS i.e. on how to dothings within AIMS.Please refer to the AIMS support contract formore information.If you are not sure your network is suitable forAIMS, please contact either by email at******************.uk 2806.AIMS Installation GuidePre-RequisitesYou must have Microsoft SQL Server installed and running, before your run the AIMS installation. The person running the installation should have administrator privileges in SQL Server. For more information, see the section headed Microsoft SQL Server configuration for more information.InstallationTo install the AIMS software, simply download the AIMS Installer and run it, following the on-screen instructions.The AIMS server installation routine performs the following tasks:∙Connects to the Microsoft SQL Server∙Creates the AIMS database∙Creates the AIMS.ini file∙Creates the AIMS Admin user∙Installs the AIMS application AIMS.exeBy default, the AIMS software will be installed in C:\Program Files\AIMS, orC:\Program Files (x86)\AIMS if you have a 64 bit version of Windows. You may wish to change this location. AIMS users will need read-only access to the installation directory, in order to be able to run the software and see the documentation. ShortcutsThe installation will place an AIMS icon on your desktop, to launch the software, and it will create shortcuts on the start menu, in a folder called AIMS.Figure 1: Start Menu ShortcutsAIMS– Use this link to launch the AIMS software.AIMS Configuration Guide– This guide leads you through the process of configuring the software, helping you decide which options are best for your organisation.AIMS Documentation–This link takes you to where the AIMS documentation is stored on disk.AIMS Installation GuideAIMS Help– This link opens the full AIMS help guide. You can also open this guide from within the software using the Help menu, or by pressing the F1 key.You will probably want to copy these shortcuts on all the AIMS client machines. Directory StructureThe installation creates a number of folders within the location you specified during the installation process.Figure 2: Directory StructureDocumentation - This folder contains all the AIMS documentation, divided in to subdirectories.Classification schemes - These are the subject classifications that are available for use as the main description of problems brought to you by clients.Templates - This folder contains example Word mailmerge templates.This section summarises some of the SQL Server configuration options required for a successful AIMS installation. The screenshots are taken from two tools –‘SQL Server Configuration Manager’ and ‘SQL Server Management Studio’. If you are using an Express version of SQL Server you may not have SQL Server Management Studio installed, but you can download it free from Microsoft.If you are using SQL Server 2000, ‘SQL Server Configuration Manager’ replaces three programs –‘Service Manager’, ‘Server Network Utility’, and ‘Client Network Utility’ but still provides the same configuration options.Likewise, ‘SQL Server Management Studio’ replaces the old ‘Enterprise Manager’ tool but has very similar functionality.SQL Server Instance NameL aunch the SQL Server Configuration Manager, select ‘SQL Server Services’ in the left hand panel, and check to see if the SQL Server state is ‘Running’. Start Mode should be set to ‘Automatic’. The name in brackets, in this case ‘SQLEXPRESS’, is the instance name. You will need this name, and the name of the machine on which the SQL Server is running, in order to configure AIMS.You do not have to have the SQL Server Browser service running if you are using the default TCP/IP port settings for SQL Server. However, if your clients are unable to connect to the SQL Server, start the SQL Server Browser service and try again.Network ProtocolAIMS clients use the TCP/IP protocol to communicate with the SQL Server. Ensure that this protocol is enabled for both the server and the clients. By default, in more recent versions of SQL Server, this protocol is turned off as a security precaution. Enable the protocol by right-clicking on the protocol name and selecting ‘enable’.AIMS Installation GuideYou also need to enable the TCP/IP protocol for the SQL Native Clients, again, right-click on the protocol name and select ‘enable’.You need to stop and re-start the SQL Server for these changes to take effect. Select the SQL Server Services icon in the left-hand panel to restart the server.FirewallsBecause AIMS uses TCP/IP to communicate with the SQL Server, you need to ensure that the firewall software on your client and server machines is allowing communication to take place on the SQL Server port. Refer to the SQL Server documentation for more information.You do not need to leave the other protocolsenabled. However, in earlier releases of SQLServer 2005 there was a bug that meant if youonly enabled TCP/IP, although it appeared enabled it was not. The work around was toenable all protocols, re-start the server, thendisable the unwanted protocols and re-startagain.AIMS Installation Guide 64-bit Versions of WindowsIf you are using a 64-bit version of Windows, ensure that you install and configure the 32-bit versions of the SQL Server native client. Because AIMS is a 32-bit program it uses the 32-bit client to communicate with the server. The server can be either 32-bit or 64-bit, it doesn’t matter.SQL Server PermissionsWhen the AIMS software connects to the database, it does so using the account details of the person logged in to Windows.For example, Freda Bloggs is logged in to Windows and wants to use AIMS. The permissions she has on the database are determined by the SQL Server administrator. They might have given her database owner (full) permissions, or just read/write permissions.W hen Freda logs in to AIMS, she enters her AIMS username “FB” and password. AIMS then tries to connect to the database using her Windows login details, and only when she is connected to the database, are her AIMS username and password checked. The permissions she has once inside the AIMS software are determined by the AIMS administrator.Note that only a user with database owner permissions for the AIMS database can add or remove user-defined fields, regardless of what permissions they have in AIMS.AIMS DatabaseAIMS SoftwareThe person installing AIMS must have ‘sysadmin’ permissions in order to create the AIMS database and grant other Windows users access to the AIMS database.In order to grant a user permissions to use AIMS, you must create a “login” and a “user” for them. In a larger organisation, you can create a group eg “AIMS Users”, and grant the permissions to the group, and then in the Windows Network Server you can add individual Windows users to that group.SQL Server LoginsThe screen below shows how to locate the server-wide user logins, and the inset image shows the properties for the login ‘RobertDesktop\Robert’ with the ‘sysadmin’ permission.AIMS Installation GuideIn the screen below, note that we have selected the ‘Security’ folder at the first leve l in the hierarchy. This is where Logins are located. Do not confuse this folder with the security folder located within each database.To create a new login, right-click the Logins folder, shown above, and select ‘New Login...’ Fill in the Login Name, usually the same name used to log in to Windows, and if you are using Windows Authentication, select the ‘Windows Authentication’ radio button, and save. If you are not using Windows Authentication, see the next section, however we strongly recommend using Windows Authentication in order to secure your data. There is no need to change the Server Roles or any other settings.SQL Server UsersRobert can now connect to SQL Server, but he still has no permission to use the AIMS database. In order to use AIMS, he must be a user of AIMS.Each database also has a ‘Security’ folder as one of its sub-folders. These folders contain the users of that database. The user and the login are related but different. Before you can create a user, you must first have created a Login – see above.To create a user, find the AIMS database underneath the Databases folder. Remember that the database may have a different name in your system. In the screen below, you can see that we have opened the Databases folder, selected the AIMS database, and under that folder we have located the security folder. Note that the folder underneath is called ‘Users’, not ‘Logins’.Right-click the Users folder and select ‘New User...’. You should see a screen like the one shown below. Enter a User name for the user, and select the Login name for that user. They need not be the same, but it is less confusing if they are.In the sectio n “Database Role membership”, you can either select ‘db_owner’ for the AIMS administrator, or ‘db_datareader’ and ‘db_datawriter’ for AIMS users without administrator privileges within AIMS.AIMS gives administrators the ability to create user-defined fields, and to do this it modifies the database structure. For this functionality to work, you must specify‘db_owner’.Lasa strongly recommends that you use windows authentication with SQL Server in order to secure your data. You can use the user administration options in the AIMS software to link AIMS users to Windows logins, to simplify the sign-in process.If you are using Windows Authentication, then you can skip this section.If you choose not to use Windows Authentication, then your SQL Server must be configured to use ‘SQL Authentication’. In Microsoft SQL Server Management Studio, right-click your SQL Server instance and select ‘Properties’.In the left-hand pane of the properties window, select the ‘Security’ page. In the top section, Server Authentication, select the option for SQL Server and Windows Authentication mode. In this mode, you will be able to create Logins which are not linked to a Windows user, and from these logins you can create AIMS users.In a non-Windows Authenticated system, all AIMS Logins and Users have the prefix ‘AIMS_’. The suffix is the User ID used inside the AIMS software itself.For example, AIMS is installed with a default U ser ID ‘ADMIN’. You can see the login AIMS_ADMIN and under the AIMS database, the user AIMS_ADMIN. The “AIMS_” prefix is used to distinguish AIMS users from any other logins in the SQL Server. Each Login is given the same password, ‘AIMS’. Clearly this is insecure, and this is why we recommend using Windows Authentication instead!The screens below show the Logins and the Users in a non-Windows Authenticated AIMS installation.If you migrated your database from Access to SQL Server, and you did not choose the Windows Authentication option, these logins will have been created for you automatically. Also, if you add new users in AIMS and you are not using Windows Authentication, it will create the logins, but to do so the AIMS administrator must have sysadmin permissions in SQL Server.Once you have installed the AIMS application and SQL Server database on your server the client workstations can be configured. We recommend you complete the client installation on one machine and test it before configuring the remaining clients. If your client cannot connect to AIMS, see the troubleshooting sections that follow this section.1. Modern versions of Windows come with SQL Server client software built in. Iffor some reason yours does not, download and install the client for both the version of Windows on the client and the version of SQL Server you are using. 2. On the Windows desktop, create a shortcut to the AIMS.exe file on yourserver. You should also create a shortcut to the AIMS Help pdf file on theserver.You should now be able to open AIMS successfully. Double click the shortcut to the 'AIMS.exe' on the desktop to check that this is so. If AIMS has not been opened before, clicking the shortcut should take you to the 'AIMS - licence Key' screen otherwise the 'AIMS - Login' screen will be displayed..AIMS uses the SQL Server Native Client on theclient workstations to connect to the SQLServer. Look on a version for your client and server.The SQL version of AIMS requires two differentkeys to be added to activate the system. Thelicence key switches the system on and thesubscription key activates the reports module.See the final section of this documentActivating the License and Subscription Keys fordetails of how to enter your subscription keyDo not enter any data until you have read thepre-configuration guide.The AIMS network installation is designed to be as simple and flexible to install andmaintain as possible. The AIMS software, manuals and client installation programs are installed on the network file server so they are accessible from each client workstation.Client machines simply use a shortcut link to the AIMS program file (AIMS.exe) on the server in order to run AIMS. This means that if you need to upgrade the program at some future time, you only need to it in one place. Information about the database server required to make a database connection is kept in a text file, AIMS.ini, installed in the same location as AIMS.exe.If you have problems getting AIMS to run and connect to the database, please follow the steps below.On the client machine:1. Check that the shortcut to the AIMS.exe is pointing to the AIMS.exe fileinstalled on your server. There should not be an AIMS.exe file on the clientmachine.2. If AIMS runs but is unable to connect to the database, ensure you have theSQL Server native client installed on the client machine, it is usually pre-installed as part of Windows. Also, check the contents of the AIMS.ini file onthe server3. If you are trying to connect to SQL Server without using WindowsAuthentication and you see the warning like the one below, then your SQLServer is not configured to allow connections using SQL Serverauthentication. See the section on Microsoft SQL Server Configuration, above.However, we strongly recommend using Windows Authentication.If you have any problems setting up AIMS, pleaseread this section before contacting AIMS team.On the server machine:1. Check the SQL Server is installed and running2. Check the AIMS.INI file. This file is automatically configured during theinstallation of the AIMS application, on the server.Browse to the folder where you installed the AIMS program (AIMS.exe) andyou should find the AIMS.ini file there. Open it using Notepad or another plain text editor. It should look similar to the example below:The first line should say “Server=<Machine>\<Instance>” where <Machine>must be the correct name for the machine where SQL Server is running, and <Instance> is the name of the SQL Server instance where the AIMS database is installed. In the above example, the machine is ‘ROBERTDESKTOP’ andthe instance is ‘SQLExpress’. For more information about instance names,see the section on SQL Server Configuration, above.The line “Database=” must have the correct name of the AIMS database inSQL Server. By default this is ‘AIMS’ but it is possible that your installationmay be different.If you are using Windows Authentication, as recommended, then the final line should say “WindowsAuthentication=True”. If you are not using WindowsAuthentication, then change this line to “WindowsAuthentication=False”. Formore information about windows authentication, see the section on SQLServer Configuration, above.Save any changes you make to the AIMS.ini file, taking care that Notepaddoes not save the file as “AIMS.ini.txt”. There is no need to re-start the SQLServer, just re-start AIMS on a client machine.3. Refer to the SQL Server Configuration section, above, and ensure that youhave enabled the TCP/IP protocol in BOTH the network and native clientareas of the SQL Server Configuration Manager. Make sure that the port you are using is not firewalled on the client or server machines.4. If you are not using the default TCP/IP port, 1433, for SQL Server you shouldensure that the SQL Server Browser service is started on the server.5. 64-bit Windows Clients: If you are installing AIMS on a 64-bit version ofWindows, you still need to install a 32-bit SQL Server client because AIMS is a 32-bit application.Once you have successfully loaded AIMS, on opening it you will be asked to login (User ID= Admin, Password= password), after which you will be asked to provide a 12 character Licence Key to activate it. This switches AIMS on and allows you to start configuration. Please read the Configuration Guide carefully as certain choices cannot be changed once any data is entered.The SQL Server version of AIMS requires two different keys to be added to activate the system. The licence key switches the system on and the subscription key activates the reports module.AIMS SQL Server needs an annually renewable subscription Key. Your 9 characterSubscription key can be found on the invoice and in the box at the bottom of the renewal letter.The 9 character Subscription Key activates the reports module. The Subscription Key only works in conjunction with the correct AIMS Licence Key which will already have been encoded.To input your Subscription Key you will need to be logged into AIMS as an administrator. Make sure no-one else is in the database. Go to the Admin drop down from the main menu bar and select Subscription Key.Now fill in the boxes putting three characters in each box. Or if updating with a subsequent years subscription renewal, over write the existing key details. The subscription expiry date will be updated the next time you log in to AIMS.End.Do not add any test data until you have read thepre-configuration guide.。

SQL Server的安装步骤

SQL Server的安装步骤一、双击SQL Server安装文件夹中的setup.exe应用程序，屏幕上出现“SQL Server安装中心”窗口，选择“安装”选项卡，单击“SQL Server独立安装或向现有安装添加功能”选项。

二、进入“安装程序支持选择”窗口，只有通过安装程序支持规则，安装程序才能继续进行，然后单击“确定”按钮。

三、进入“功能选择”窗口，单击“全选”按钮。

四、单击“下一步”按钮进入“实例配置”窗口，选择“默认实例”单选按钮，在“实例ID”文本框中将n自动填入MICSQLSERVER，单击“下一部”按钮。

五、选择“对所有SQL Server服务使用相同的账户”，此时将出现一个新窗口，在“账户名”文本框中输入“NT AUTHORITY\SYSTEM”,单击“确定”按钮。

六、单击“下一步”按钮进入“数据库引擎配置”窗口，选择“混合模式”单选按钮，单击“添加当前用户”按钮，在“指定SQL Server管理员”框中将自动填入“dell-PC\dell(dell)”，在“输入密码”和“确认密码”文本框中设置密码为“123456”。

七、单击“下一步”按钮进入“Analysis Services配置”窗口，单击“添加当前用户”按钮，在“指定哪些用户具有Analysis Services的管理权限”框中将自动填入“dell-PC\dell(dell)”，单击“下一步”按钮。

八、在“Reporting Services配置”窗口、“错误和使用情况报告”窗口都单击“下一步”按钮，进入“安装配置规则”窗口，单击“下一步”按钮进入“准备安装”窗口，单击“安装”按钮进入“安装进度”窗口，单击“下一步”按钮进入安装过程，安装完成后单击“下一步”按钮。

九、进入“完成”窗口，单击“关闭”按钮完成全部安装过程。

Sql server安装详细步骤以及安装过程

原因：原因：当出现这个错误时，是因为在注册表删除了 HKEY_LOCAL_MACHINE\SOFTWARE\ HKEY_LOCAL_MACHINE\SOFTWARE\O DBC中有关sql sever的信息 DBC中有关sql sever的信息
（3）解决方法：解决方法：这时可以选择修复注册表，或安装ODBC修这时可以选择修复注册表，或安装ODBC修复工具我在“管理工具”下的“数据源（ODBC）我在“管理工具”下的“数据源（ODBC）” 中没有找到安装ODBC Driver相关内容。产中没有找到安装ODBC Driver相关内容。产生这个问题的原因是某些使用ODBC数据源生这个问题的原因是某些使用ODBC数据源的程序，在卸载的时候，会将ODBC 的程序，在卸载的时候，会将ODBC Driver 的信息都删除掉。事实上，我们只需要用odbcconf.exe来重新事实上，我们只需要用odbcconf.exe来重新注册一下ODBC Driver就可以了。注册一下ODBC Driver就可以了。
在Windows/System32目录下有几个脚本文件，可以来完成 Windows/System32目录下有几个脚本文件，可以来完成驱动程序的注册： odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\mdaccore.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\sqlclnt.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\odbcconf.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\redist.rsp 通过在dos命令行中运行上述命令，则odbcconf.exe 通过在dos命令行中运行上述命令，则odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\mdaccore.rsp %systemroot%\system32\ odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\sqlclnt.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\odbcconf.rsp odbcconf.exe /S /Lv odbcconf.log /F %systemroot%\system32\ %systemroot%\system32\redist.rsp

SQL Server的安装与配置

SQL Server的安装与配置SQL Server的安装使用相对Access来说要复杂很多，因此本章将会详细介绍它的安装使用。

SQL Server是目前中小型数据库中使用最为广泛的数据库，因此作为一个数据库开发人员，这是必须要掌握的。

SQL Server 2000目前有好几个版本，通常在Windows 2000操作系统上安装企业版，而在Windows 98等操作系统上安装标准版。

推荐使用企业版，本节将介绍企业版的安装使用。

1 SQL Server安装实例准备好SQL Server安装盘以后，进入安装目录，双击“SETUP.exe”文件，进入安装界面（很多时候安装程序会自动运行），如图1所示。

如果是Windows 2000或者是Windows XP操作系统，则直接单击“安装SQL Server 2000组建”进行安装，如果是Windows 98，则有可能需要先安装“安装SQL Server 2000先决条件”，由于作者采用Windows XP操作系统，所以直接单击第一项安装，进入安装组件界面，如图2所示。

图1 数据录入、编辑界面图2 安装组件界面在图2中，单击“安装数据库服务器”（其他两个选项一般不用），进入安装向导界面，如图3所示。

在图3中，选择“本地计算机”单选按钮，然后单击按钮“下一步”，进入选择安装计算机界面，如图4所示。

图4主要是让用户选择数据库要安装的计算机，通常是默认安装在本地计算机上，其中“远程计算机”是将数据库安装在另外一台计算机上，不过很少使用，也就不多介绍。

单击按钮“下一步”，进入如图5所示界面。

图3 安装向导图4 选择数据库安装的计算机图5是让读者选择创建一个新的SQL Server实例，默认选择是第一项，而“高级选项”则是设定安装程序，使得安装在无人的情况下也能够安装，不鼓励使用。

这里不改变选择，直接单击按钮“下一步”，进入下一个界面，如图6所示。

图5 选择安装SQL Server实例图6 输入用户信息图6没什么用处，是让用户输入一些基本的信息，单击按钮“下一步”，进入下一个界面如图7所示。

sql server安装教程

sql server安装教程SQL Server是由微软公司开发的关系数据库管理系统，在企业数据管理中广泛应用。

下面是SQL Server的安装教程，共500字。

SQL Server的安装步骤如下：步骤一：下载SQL Server安装程序首先，你需要从微软官方网站下载SQL Server的安装程序。

请注意，SQL Server有多个版本，如Developer、Express和Standard等。

选择适合你需求的版本并下载安装程序。

步骤二：运行安装程序双击安装程序来开始安装。

在安装窗口中，你需要选择安装语言和点击“下一步”继续。

步骤三：接受许可协议阅读许可协议，并接受协议条款。

然后点击“下一步”。

步骤四：选择安装类型在安装类型窗口中，你可以选择“新建独立SQL Server安装或添加功能到现有安装”或“添加新功能到已存在的SQL Server 实例”。

选择适合你需求的选项，并点击“下一步”。

步骤五：选择安装功能在此窗口中，你可以选择你想要安装的具体功能，如数据库引擎服务、分析服务和报告服务等。

选择你需要的功能，并点击“下一步”。

步骤六：安装规则检测系统将检测你的计算机是否满足SQL Server的安装要求。

一般来说，系统会自动检测并显示结果。

如果你的计算机满足要求，点击“下一步”继续。

步骤七：实例配置在实例配置窗口中，你可以选择默认实例或命名实例。

默认实例使用默认配置，而命名实例可以自定义配置。

选择你需要的配置，然后点击“下一步”。

步骤八：服务器配置在服务器配置窗口中，你需要设置SQL Server的身份验证模式和相应的登录凭据。

你可以选择Windows身份验证模式或混合身份验证模式。

选择你需要的模式，并设置登录凭证。

步骤九：数据目录在此窗口中，你需要指定数据库文件和日志文件的安装目录。

点击“下一步”继续。

步骤十：安装规则检测再次进行安装规则检测，确保你的计算机满足要求。

点击“下一步”继续。

步骤十一：准备安装在此窗口中，你可以查看安装设置的摘要。

自己整理的SQL-server详细安装步骤

自己整理的SQL-server详细安装步骤一、数据库的安装。

1.首先打开安装文件，选择SQLServerx86文件夹，点击安装完成后再点击安装。

（一）安装Tools文件1.点击接受许可条款和条件，点击下一步。

2.进入下一步，点击安装。

3.点击安装。

4，点击下一步。

5.选择我接受许可协议中的条款，点击安装。

6.点击下一步。

7.点击安装客户端组件和文档、实例和实例数据库，选择安装全部组件。

8，安装完成点击下一步。

9.点击下一步。

10.点击下一步。

11点击安装，开始安装。

12.安装完毕，点击下一步。

13.点击完成，安装完成。

二．点击安装server文件。

1.点击接受许可条款和条件，点击下一步。

2.进入下一步，点击安装。

3.点击安装。

4，点击下一步。

5.选择我接受许可协议中的条款，点击安装。

6.点击下一步。

7.点击下一步。

8.选择全部，点击下一步。

9.选择默认实例，点击下一步。

10.选择使用内置系统账户为本地系统，点击下一步。

11.选择混合模式，设置密码，点击下一步。

12.点击下一步。

13.点击下一步。

14.点击安装，开始安装。

15.安装完毕，点击下一步。

16.点击完成，安装完成。

三、数据库的约束表达式。

选择要约束的项，点击右键CHECK约束/选择表设计器。

进入CHECK约束编辑约束属性，点击添加，在常规栏里书写约束表达式，添加说明。

四、数据库的导入、导出。

导入：1右击对象资源管理器的空白，选择任务-->导入数据。

2、点击下一步，在新打开窗口中选择数据源：Access,Excel等，选择文件路径，点击下一步。

3、在窗口中选择目标、身份验证、点击下一步。

4、在弹出窗口中选择“复制一个或多个表或视图数据。

点击下有一步。

5、在选择源表和源视图窗口中，选择要复制的表或视图。

6、在保存并执行窗口中，点击下一步。

7、点击完成，开始复制。

最后点击关闭。

导出;1.在对象资源管理器重右击选择任务—>导出数据命令。

安装说明

格林财务管理系统（for Sql_Server）安装说明格林财务软件是根据我国财政部现行的会计制度、税收制度以及会计人员的工作习惯，并充分发挥计算机特点，研制开发出来的一套功能强大、技术领先、安全稳定、易学易用的商品化通用财务软件，适用于各种大、中、小企事业单位。

一、如何安装格林财务管理系统（以下简称“本系统”）？请将本系统的安装光牒放入计算机的光驱中，打开本系统的安装目录。

1、本软件为绿色软件，只需将光盘根目录下的(GreenSoft)目录复制到您的计算机中即可使用，但您需要自已建立桌面快捷方式。

2、您也可以通过安装程序自动完成安装任务，双击“SETUP.EXE”文件，开始安装。

注意：1、如果用户的操作系统是WINDOWS98第二版以上的版本，则安装完毕后即可使用。

否则，请安装光牒中的“ADO”数据库引擎(MDAC2.7目录中的文件)。

2、Sql_Server2000演示数据在光盘的“Sqlcwgl.bak”文件中，该文件是Sql_Server2000的备份文件，需要将其恢复到Sql_Server2000中才能使用(详见Sql_Server 演示数据说明)。

如果您已将其恢复，那么，您可在登录窗口中新建链接即可。

二、如何建立一个属于自己的帐套？1、在“系统登录”窗口中单击“新建帐套”安钮，打开“新建帐套”窗口，输入符合用户条件的数据。

建立用户所指定年份的帐套。

或在“帐套属性”窗口中，也具有该功能。

2、择Sql_Server数据库时，应安装MICROSOFTSql_Server2000。

3、选择好新建的帐套后，使用“超级用户”登录。

3、打开“基础设置”界面，单击“用户管理”图标，打开“用户与权限”窗口，划分用户权限。

4、击“会计科目”按钮，打开“会计科目”窗口，用户可根据实际情况，建立会计科目，并录入年初余额（年初余额必须平衡）。

5、单击“凭证属性”图标，打开“凭证属性设置”窗口，用户可以在该窗口中设置“收、付、转”或“通用”格式。

sqlserver中文参考手册

SQL Server中文参考手册一、介绍SQL Server是微软公司开发的一款关系型数据库管理系统，常用于企业级应用程序的开发和数据管理。

它具有强大的数据处理和管理能力，能够支撑大型的数据量和复杂的业务逻辑。

本文将针对SQL Server的中文参考手册进行详细介绍，帮助读者理解和使用SQL Server的各项功能。

二、安装与配置1. 下载与安装在微软全球信息站上可以找到SQL Server的安装程序，根据自己的需求选择相应的版本进行下载。

安装过程中，可以根据向导逐步进行配置，包括选择安装目录、设置数据库引擎配置、配置实例等。

2. 服务设置安装完成后，需要对SQL Server的各项服务进行设置，包括SQL Server数据库引擎服务、SQL Server代理服务等。

可以通过“SQL Server配置管理器”进行相关设置。

三、数据库设计与管理1. 数据库设计SQL Server支持基于数据库模型进行设计，包括创建表、定义字段、设置键与索引等。

可以使用SQL Server Management Studio （SSMS）进行数据库设计。

2. 数据库管理SQL Server提供了丰富的数据库管理功能，包括备份与还原、数据库迁移、容灾与恢复等。

通过SSMS可以轻松进行数据库的管理操作。

四、数据查询与处理1. SQL语法SQL Server支持标准的SQL语法，包括SELECT、INSERT、UPDATE、DELETE等操作。

还支持存储过程、触发器、函数等高级特性。

2. 查询优化SQL Server提供了查询优化器，可以对查询语句进行优化，提高查询效率。

通过执行计划或查询分析工具，可以对查询进行性能分析。

五、安全与权限管理1. 登入与用户SQL Server允许创建多个登入账号，并且可以为不同的数据库设置不同的用户权限。

通过SQL Server安全性功能可以进行相关设置。

2. 数据加密SQL Server支持数据加密功能，可以对敏感数据进行加密保护。

sql server安装方法

sql server安装方法
嘿，朋友们！今天咱就来唠唠 SQL Server 的安装方法。

这可不像你想象的那么难哦，就像骑自行车，一旦掌握了诀窍，那就是小菜一碟啦！
首先呢，你得准备好安装所需的东西，就好比做饭得先有食材一样。

确保你的电脑满足系统要求，不然可就像小马拉大车，费劲咯！
然后，找到 SQL Server 的安装文件，就像找到打开宝藏的钥匙。

接下来就开始安装啦！在安装过程中，要仔细看每一个步骤，别像个小
马虎似的一带而过。

这就好比走迷宫，得看清路才能走得顺溜呀。

安装向导会一步一步引导你，就像个贴心的小导游。

它会让你选择
安装的组件，这时候你可得根据自己的需求来选哦，别瞎选一气，不
然到时候用起来发现不对劲，那不就傻眼啦！
在设置数据库引擎的时候，要想好怎么配置，这可关系到后续的使
用效果呢。

就好像给房子打地基，得牢固才行。

还有啊，身份验证模式也很重要呢！就像给家门配钥匙，得选个安
全又方便的方式。

安装过程中可能会遇到一些小问题，别慌！这就跟路上遇到小石子
一样，踢开就行啦。

比如说可能会提示缺少某些组件，那就赶紧去补上。

等安装完成后，别着急庆祝，先去测试一下，看看是不是一切都正常运行。

就像新车子到手，得先试驾一圈嘛。

哎呀，其实安装 SQL Server 真的没那么难啦！只要你耐心点，仔细点，按照步骤来，肯定能轻松搞定。

就好像搭积木，一块一块稳稳地搭起来，最后就能建成漂亮的城堡啦！大家加油哦，相信你们都能成功安装 SQL Server，然后在数据库的世界里畅游无阻！。

安装SQL Server详细图解

安装SQL Server1、将Microsoft SQL Server 的第一张光盘插入光盘驱动器中，选择“服务器组件、工具、联机丛书和示例”，进行安装(图1)。

图12、接受“最终用户许可协议”窗体中(图2)，单击“下一步”按钮。

3、在“安装必备组件”窗体中(图3)，单击“安装”按钮，安装完成后单击“下一步”按钮。

图34、在“欢迎使用Microsoft SQL Server安装向导”窗体中(图4)，单击“下一步”按钮。

图45、在“系统配置检查”窗体中(图5)，安装程序将对系统配置进行检查，检查成功后，单击“下一步”按钮。

图56、在“注册信息”窗体中(图6)，输入姓名、公司和产品密钥，单击“下一步”按钮。

图67、在“要安装的组件”窗体中(图7)，勾选“SQL Server Database Services”等组件，单击“下一步”按钮。

图78、在“实例名”窗体中(图8)，选择默认实例，单击“下一步”按钮。

9、在“服务账户”窗体中(图9)，选择使用系统内置账户，单击“下一步”按钮。

图910、在“身份验证模式”窗体中(图10)，选择“混合模式(Windows身份验证和SQL Server身份验证)”，输入sa的密码和确认密码(必须包含大小写字母、数字和特殊字符且长度不少于8位)。

11、在“排序规则设置”窗体中(图11)，单击“下一步”按钮。

图1112、在“错误和使用情况报告设置”窗体中(图12)，单击“下一步”按钮。

13、在“准备安装”窗体中(图13)，单击“安装”按钮。

图1314、在“安装进度”窗体中(图14)，单击“下一步”按钮。

图1415、在“完成Microsoft SQL Server 安装”窗体中(图15)，单击“完成”按钮。

图1516、将Microsoft SQL Server 的第二张光盘插入光盘驱动器中，选择“仅工具、联机丛书和示例”，进行安装(图16)。

图1617、接受“最终用户许可协议”窗体中(图17)，单击“下一步”按钮。

sql server操作手册

SQL Server操作手册一、简介SQL Server是由微软公司开发的关系数据库管理系统，广泛应用于企业级数据管理和处理。

本手册旨在为用户提供SQL Server的操作指南，帮助用户熟练掌握SQL Server的基本操作和高级功能。

二、安装和配置1. 下载SQL Server安装包用户可以从微软冠方全球信息站下载SQL Server的安装程序，选择适用于自己系统的版本进行下载。

2. 安装SQL Server双击安装程序，按照指引进行安装。

在安装过程中，用户需要选择安装的组件、配置数据库实例、设置管理员账号等信息。

3. 配置SQL Server安装完成后，用户需要进行SQL Server的配置工作，包括设置数据库连接、调整性能参数、配置备份策略等。

三、基本操作1. 连接数据库用户可以使用SQL Server Management Studio（SSMS）等工具连接到数据库实例，输入正确的服务器名、用户名和密码进行连接。

2. 创建数据库通过SSMS或者T-SQL语句，用户可以创建新的数据库，指定数据库的名称、文件路径、文件大小等参数。

3. 创建表在数据库中创建表格，定义表格的字段、数据类型、约束等信息，为数据存储做准备。

4. 插入数据使用INSERT语句向数据库表格中插入数据，确保数据的完整性和正确性。

5. 查询数据使用SELECT语句查询数据库表格中的数据，根据条件筛选出符合要求的数据。

6. 更新和删除数据使用UPDATE和DELETE语句更新和删除数据库表格中的数据，确保数据的实时性和准确性。

四、高级功能1. 存储过程用户可以使用T-SQL语句创建存储过程，实现对数据库的一系列操作逻辑的封装和复用。

2. 触发器使用触发器可以在数据库表格发生特定事件时自动执行特定的操作，实现数据的自动化处理和监控。

3. 索引优化通过合理地创建各种类型的数据库索引，可以提高数据库的查询性能和数据检索速度。

4. 备份恢复制定定期备份数据库的策略，并了解如何灵活、高效地进行数据库的恢复操作。

SQL SERVER安装ODBC配置说明文档

MTC4后台监控系统SQLServer数据库应用说明书文件编号:__________________ 版本号:__________________ 发放编号:__________________ 持册人:__________________长沙华能自控集团有限公1引言 (3)1.1编写目的 (3)1.2背景 (3)1.3定义 (4)1.4参考资料 (4)2用途 (4)2.1功能 (4)2.2性能 (4)2.2.1精度 (4)2.2.2时间特性 (5)2.2.3灵活性 (5)2.3安全保密 (5)3运行环境 (5)3.1硬设备 (5)3.2支持软件 (5)3.3数据结构 (6)4使用过程 (6)4.1安装与初始化 (6)4.2软件使用 (6)4.3文卷查询 (21)4.4出错处理和恢复 (21)4.5终端操作 (21)1引言1.1编写目的本手册是MTC后台软件数据库部分关于SQL SERVER数据库的配置调试使用手册，通过对各种配置参数来来说明如何配置调试数据库接口，并实现MTC后台对SQL SERVER 数据库的扩展。

本使用手册主要面向用户是公司内部开发部门和售后服务部门软件维护的相关人员，以及对采用MTCT后台系统的数据库方式有更深了解的用户人群。

1.2背景SQL SERVER数据库是一个全面的、集成的、端到端的数据解决方案，它为企业中的用户提供了一个安全、可靠和高效的平台用于企业数据管理和商业智能应用。

SQL Server 为IT专家和信息工作者带来了强大的、熟悉的工具，同时减少了在从移动设备到企业数据系统的多平台上创建、部署、管理及使用企业数据和分析应用程序的复杂度。

通过全面的功能集、和现有系统的集成性、以及对日常任务的自动化管理能力，SQL Server为不同规模的企业提供了一个完整的数据解决方案。

MTC后台相关数据库的程序，通过采用ADO数据直连，采用ODBC数据方式直接对数据库进行操作。

SQL Server 2012 Enterprise 安装指南说明书

Test Lab Guide: Install SQL Server 2012 EnterpriseThis document is provided “as-is”. Information and views expressed in this document, including URL and other Internet Web site references, may change without notice. You bear the risk of using it.Some examples depicted herein are provided for illustration only and are fictitious. No real association or connection is intended or should be inferred.This document does not provide you with any legal rights to any intellectual property in any Microsoft product. You may copy and use this document for your internal, reference purposes.© 2012 Microsoft Corporation. All rights reserved.Test Lab Guide: Install SQL Server 2012 EnterpriseJames MoreyMicrosoft CorporationApril 2012Applies to: SQL Server 2012 EnterpriseSummary: This paper contains a brief introduction to SQL Server 2012 Enterprise and step-by-step instructions for installing SQL Server 2012 Enterprise on the APP1 computer in the base configuration test lab.ContentsContents (2)Introduction (2)In this guide (3)Test lab overview (3)Hardware and software requirements (4)Steps for Installing SQL Server 2012 Enterprise (4)Step 1: Set up the Base Configuration Test Lab (5)Step 2: Install SQL Server Prerequisites (5)Step 3: Install SQL Server 2012 Enterprise (6)Step 4: Verify the installation (7)Snapshot the Configuration (7)Additional Resources (8)IntroductionSQL Server 2012 delivers several breakthrough capabilities that enable your organization to scale database operations with confidence, improve IT and developer efficiency, and enable highly scalable and well managed business intelligence on a self-service basis for your users. These capabilities include the following:•Trusted, Scalable Platform - Supporting data consistency across heterogeneous systems through SQL Server Master Data Services, enabling high-scale complex event-streamprocessing through SQL Server StreamInsight™, and supporting scale-up scenarios for the largest available x64 and Itanium hardware (up to 256 logical processors).•IT & Developer Efficiency - Enabling administrators to centrally monitor and manage multiple database applications, instances or servers, accelerating the development and deployment of applications and providing improved support for virtualization through Hyper-V with Live Migration in Windows Server 2008 R2.•Managed Self-Service BI - Expanding powerful BI tools to all users with SQL Server PowerPivot for Excel and empowering a new class of business users to build and sharepowerful BI solutions with little or no IT support, while still enabling IT to monitor and manage user-generated BI solutions.For more information about SQL Server 2012, see the SQL Server Product Information site. In this guideThis paper contains instructions for setting up a test lab based on the Base Configuration test lab guide and configuring SQL Server 2012 Enterprise on a pre-existing server computer. The resulting test lab can be used to build out other test lab configurations that need a SQL server.ImportantThe following instructions are for configuring SQL Server 2012 Enterprise in a test lab using the minimum number of computers. Individual computers are needed to separate theservices provided on the network and to clearly show the desired functionality. Thisconfiguration is neither designed to reflect best practices nor does it reflect a desired or recommended configuration for a production network. The configuration, including IPaddresses and all other configuration parameters, is designed only to work on a separate test lab network.Attempting to adapt this SQL Server 2012 Enterprise test lab configuration to a pilot or production deployment can result in configuration or functionality issues. To ensure proper configuration and operation for your pilot or production SQL Server 2012 Enterprisedeployment, use the information in Installation for SQL Server 2012.Test lab overviewIn this test lab, SQL Server 2012 Enterprise is deployed with:∙One computer, named DC1, that runs Windows® Server® 2008 R2 Enterprise Edition and that is configured as an intranet domain controller, Domain Name System (DNS) server, DHCP server, and enterprise root certification authority (CA).∙One intranet member server, named APP1, which runs SQL Server 2012 Enterprise. Note that the instructions in this paper can also be used to install SQL Server 2012 Enterprise ona different intranet member server.∙One member client computer, named CLIENT1, which runs Windows 7 Enterprise or Ultimate.The test lab consists of a single subnet named Corpnet (10.0.0.0/24) that simulates a private intranet. Computers on the Corpnet subnet connect by using a hub or switch. See the following figure.Note that this figure does not include a different intranet member server in your test lab on which SQL Server 2012 Enterprise could be installed.Hardware and software requirementsThe following are required components of the test lab:∙The product disc or files for Windows Server 2008 R2.∙The product disc or files for Windows 7.∙The product disc or files for SQL Server 2012 Enterprise. See Microsoft SQL Server 2012 Evaluation – 64-bit a trial version.∙Two computers that meet the minimum hardware requirements for Windows Server 2008 R2 Enterprise Edition. For more information, see Windows Server 2008 System Requirements. ∙One computer that meets the minimum hardware requirements for Windows 7 Enterprise or Ultimate. For more information, see Windows 7 system requirements.Steps for Installing SQL Server 2012 Enterprise There are four steps to follow when installing SQL Server 2012 Enterprise.1.Set up the Base Configuration test lab.2.Install SQL Server prerequisites.3.Install SQL Server 2012 Enterprise.4.Verify the installation.NoteYou must be logged on as a member of the Domain Admins group or a member of theAdministrators group on each computer to complete the tasks described in this guide. If you cannot complete a task while you are logged on with an account that is a member of theAdministrators group, try performing the task while you are logged on with an account that is a member of the Domain Admins group.The following sections provide details about how to perform these steps.Step 1: Set up the Base Configuration Test Lab Set up the Base Configuration test lab for the Corpnet subnet by using the procedures in the “Steps for Configuring the Corpnet Subnet” section of the Test Lab Guide: Base Configuration. Step 2: Install SQL Server PrerequisitesIn this procedure, you create an organizational unit in the domain named ServiceAccounts and then create two service accounts that will be used by SQL Server 2012.To create the ServiceAccounts organizational unit and the service accounts1.On DC1, log on with the User1 account.2.Click Start, click Administrative Tools, and click Active Directory Users andComputers.3.In the tree pane of Active Directory Users and Computers, right-click, select New, and then Organizational Unit.4.In Name, type ServiceAccounts, and then click OK.5.Right-click ServiceAccounts, select New, and then select User.6.In New Object – User, in the Full Name box, type SQL Server Agent.7.In User logon name, type SQLAgent, and click Next.8.In Password and Confirm Password, type Pass1word$.9.Clear User must change password at next logon, select Password never expires,and click Next.10.Click Finish.11.Right-click ServiceAccounts, select New, and then select User.12.In New Object – User, in the Full Name box, type SQL Server Database Engine.13.In User logon name, type SQLDatabase and click Next.14.In Password and Confirm Password, type Pass1word$.15.Clear User must change password at next logon, select Password never expires,and click Next.16.Click Finish.In this procedure, you install the .NET 3.5 Framework.To install the .NET Framework 3.51.On APP1 (or the computer on which SQL Server 2012 Enterprise is being installed), logon with the User1 account.2.In Server Manager, click Features, and then click Add Features. This will launch theAdd Features Wizard and you will see the Select Features screen.3.Select .NET Framework 3.5.1 Features. This will bring up a box that asks states: Youcannot install .NET Framework 3.5.1 Features unless the required role servicesand features are also installed. Click Add Required Features. The box willdisappear. On the Select Features screen, click Next.4.On the Web Server (IIS) screen, click Next.5.On the Role Services screen, click Next.6.On the Confirm Installation Selections screen, click Install. This will begin theinstallation.7.On the Installation Results screen, click Close.Step 3: Install SQL Server 2012 EnterpriseIn this procedure, you install SQL Server 2012 Enterprise.To install SQL Server 2012 Enterprise1.On APP1 (or the computer on which SQL Server 2012 Enterprise is being installed),navigate to the directory that contains the SQL Server 2012 Enterprise binaries anddouble-click Setup.EXE. This will launch the SQL Server Installation Center.2.On the SQL Server Installation Center, on the left, click Installation.3.On the right, click New SQL Server stand-alone installation or add features to anexisting installation. This will launch the SQL Server 2012 Setup.4.On the Setup Support Rules screen, click OK. This will close the Setup Support Rulesscreen and will bring up the Product Key screen. From Specify a free version, select Evaluation. Click Next.5.On the License Terms screen, read the Licensing terms, place a check in the box nextto I accept the license terms and click Next.6.On the Product Updates screen, click Next.7.On the Install Setup Files screen, click Install. This will take a few moments tocomplete. Once this completes the Setup Support Rules screen will appear again.8.On the Setup Support Rules screen, click Next.9.On the Setup Role screen, select SQL Server Feature Installation and click Next.10.On the Feature Selection screen, under Instance Features place a check inDatabase Engine Services, under Shared Features place a check in Management Tools – Basic and Management Tools – Complete. Click Next.11.On the Installation Rules screen, click Next.12.On the Instance Configuration screen, click Next.13.On the Disk Space Requirements screen, click Next.14.On the Server Configuration screen, next to SQL Server Agent under AccountName, enter CORP\SQLAgent, under Password, enter Pass1word$.15.On the Server Configuration screen, next to SQL Server Database Engine underAccount Name, enter CORP\SQLDatabase, under Password, enter Pass1word$.16.Click Next.17.On the Database Engine Configuration screen, click Add Current User and clickNext.18.On the Error Reporting screen, click Next.19.On the Installation Configuration Rules screen, click Next.20.On the Ready to Install screen, click Install.21.On the Installation Progress screen, wait until the installation completes.22.On the Complete screen, click Close.23.Close the SQL Server Installation Center.Step 4: Verify the installationIn this procedure, you verify that installed SQL Server services are running.To verify installed SQL Server services are running1.Click Start, select Administrative Tools, and click Services.2.Scroll down to SQL Server (MSSQLSERVER) and verify that it has a status of Started.3.In Services, right-click SQL Server Agent (MSSQLSERVER), and click Start. This willstart the SQL Server Agent.4.When this completes, verify the SQL Server Agent (MSSQLSERVER) has a status ofStarted.5.Close Services.In this procedure, you verify the SQL Server 2012 Enterprise installation by connecting to the database server using SQL Server Management Studio.To connect to SQL Server 2012 Enterprise using SQL Server Management Studio1.Click Start, click All Programs, click Microsoft SQL Server 2012, and click SQLServer Management Studio.2.On the Connect to Server dialog box, under Server Type: select Database Engine.3.On the Connect to Server dialog box, under Server name: select APP1 (or thecomputer on which SQL Server 2012 Enterprise is being installed).4.On the Connect to Server dialog box, under Authentication: select WindowsAuthentication.5.Click Connect. This should be successful and the database information will be displayedon the left. The SQL Server Agent should have a green arrow.6.Close Microsoft SQL Server Management Studio.Snapshot the ConfigurationThis completes the installation of SQL Server 2012 Enterprise. To save this configuration so that you can quickly return to a working configuration from which you can test other TLGs or test lab extensions or for your own experimentation and learning, do the following:1.On all physical computers or virtual machines in the test lab, close all windows and thenperform a graceful shutdown.2.If your lab is based on virtual machines, save a snapshot of each virtual machine andname the snapshots TestLabSQLServer. If your lab uses physical computers, createdisk images to save the test lab configuration.Additional ResourcesFor more information about SQL Server 2012, see the Microsoft SQL Server product information web page.Microsoft strongly encourages you to develop and publish your own TLG content for SQL Server 2012, either in the TechNet Wiki (example: Test Lab Guide: Demonstrate Remote Access VPNs) or in your own publishing forum (example: Test Lab Guide (Part 1) - Demonstrate TMG PPTP,L2TP/IPsec and SSTP Remote Access VPN Server). If you want to publish your TLG content in the TechNet wiki, see the How to contribute series of TLG blog posts for information about the types of content you can create and for links to templates and guidance.For a list of additional Microsoft TLGs, see Test Lab Guides in the TechNet Wiki.。

sqlserver安装手册

Sqlserver安装手册一、安装虚拟光驱(由于公司采用镜像文件安装sqlserver，故首先应安装虚拟光驱) 。

1.找到虚拟光驱安装软件（daemon_tools_347cn_eric.exe）所在位置（如图1-1），双击执行，可以进行安装。

图1-12.点击进入安装向导（如图1-2）。

图1-23.点击进入选择安装选项（如图1-3）。

图1-34.选择你要安装的文件夹名(默认文件夹为C:\Program Files\D-Tools\)，点击，进入确认安装（如图1-4)。

图1-45.点击，开始安装(如图1-5)。

图1-56.点击完成安装（如图1-6）图1-67.点击，重启电脑，使配置生效（如图1-7）。

图1-78、设置虚拟驱动器。

在电脑下方工具栏找到虚拟驱动器图标（如图所示：），点击右键选择“虚拟CD/DVD-ROM”菜单下的“设置驱动器数量”菜单，然后选择“一个驱动器”选项。

二、安装sqlserver 。

1.在电脑下方工具栏找到虚拟驱动器图标（如图所示：），点击右键选择“虚拟CD/DVD-ROM ”菜单下的“驱动器0：[G] 没有媒体”菜单，再选择“安装镜像文件”，将弹出选择镜像文件对话框（如图2-1所示）：图2-12.点击“安装SQL Server 2000简体中文开发版”，开始安装sqlserver （如图2-2所示）。

图2-2点击此处，选择sqlserver镜像安装文件。

3.点击“安装SQL Server 2000组件”（如图2-3所示）。

图2-34.点击“安装数据库服务器”（如图2-4所示）。

图2-45.点击“下一步”，进入安装向导（如图2-5所示）。

图2-56、点击“下一步”，继续安装（如图2-6所示）。

图2-67.点击“下一步”，继续安装（如图2-7所示）。

图2-78.输入您的名字(可选择性输入公司名)。

点击“下一步”，继续安装（如图2-8所示）。

图2-89.点击“是”，继续安装（如图2-9所示）。

Microsoft SQL Server安装指南

Microsoft SQL Server安装指南Microsoft SQL Server 区分企业版、标准版和开发版等版本。

开发版可以在Windows 95, Windows 98, Windows Me, Windows NT, Window 2000 Professional , Windows 2000 Server, Windows XP Home, Windows XP Professional, Windows 2003 Server等操作系统安装，标准版和企业版仅能安装在Windows 的Server版本中。

讯博软件建议针对单机版安装Microsoft SQL Server开发版，针对网络版本安装Microsoft SQL Server企业版。

以下以SQL Server标准版为例讲述安装过程，其他版本的安装过程大致相同。

开始安装Microsoft SQL Server 2000以下安装过程采用SQL SERVER Standard edition(标准)中文版为例！将SQL SERVER安装光盘放入CD-ROM或相关兼容设备（DVD），SQL SERVER会自动启动安装界面，如果该光盘不自动运行，请双击该光盘根目录中的 Autorun.exe 文件。

如下图1、选择“安装SQL Server 2000组件”即可启动安装向导，安装程序于是准备 SQL Server 安装向导。

在"欢迎"屏幕中单击"下一步"按钮。

2、在"计算机名"对话框中，"本地计算机"是默认选项，并且本地计算机名出现在编辑框中。

单击"下一步"按钮。

3、在"安装选项"对话框中，单击"创建 SQL Server 新实例或安装客户端工具"选项，然后单击"下一步"按钮。

sql server安装教程

SQL Server安装教程1. 环境准备在开始安装SQL Server之前，需要确保系统满足以下要求：•操作系统：Windows 7或更高版本，Windows Server 2008或更高版本•内存：至少4GB内存•存储空间：至少需要2.5GB的可用存储空间•处理器：建议使用多核处理器2. 下载SQL Server安装文件访问Microsoft官方网站并登录您的帐户，然后在产品下载页面中找到SQL Server安装程序。

选择适合您操作系统的版本并下载安装文件。

3. 运行安装程序双击下载的安装程序文件，将会启动安装向导。

按照向导的指示逐步进行安装。

4. 安装规则在安装规则页面中，系统将对您的系统进行检测以确保满足安装要求。

如果系统存在任何问题，将会显示在这个页面上。

如果没有问题，则可以继续安装。

5. 接受许可条款在这个页面上，您需要阅读并接受SQL Server的许可协议。

阅读完协议，勾选“我接受许可条款”选项，然后点击下一步继续安装。

6. 特性选择在特性选择页面上，您可以选择要安装的SQL Server组件。

选择您需要的组件，并根据实际需求进行配置。

通常情况下，选择基本的数据库引擎服务即可，但也可以根据需要选择其他组件，如报告服务、集成服务等。

7. 实例配置在实例配置页面上，您可以选择创建一个新实例或将SQL Server安装为默认实例。

如果您只是进行个人学习或开发测试，选择默认实例即可。

如果您需要在同一台计算机上运行多个实例，选择命名实例并为其指定一个唯一的实例名称。

8. 服务器配置在服务器配置页面上，您需要指定SQL Server的认证模式。

可以选择Windows身份验证或混合身份验证。

混合身份验证允许使用Windows身份验证和SQL Server身份验证登录。

9. 数据库引擎配置在数据库引擎配置页面中，您可以设置一些与数据库引擎服务相关的高级选项。

如果您对这些选项不熟悉，可以保持默认设置。

Moebius for SQL Server用户手册

NO：Green Trend(DBC2012-JSWD-03)北京格瑞趋势科技有限公司Moebius for SQL Server用户手册© Copyright 北京格瑞趋势科技有限公司Corporation 2012. All rights reserved.目录第1章概要 (6)1.1致读者 (6)1.2文档结构 (6)1.3标记规则 (6)第2章使用MOEBIUS配置管理器 (7)2.1常规 (7)2.1.1只读 (8)2.1.2添加节点 (8)2.1.3联机 (8)2.1.4脱机 (8)2.1.5删除 (9)2.1.6设置权重 (9)2.1.7新建虚拟IP (9)2.1.8更改连接属性 (9)2.1.9修复 (9)2.2通知和监控 (9)2.3连接 (10)2.3.1标示 (10)2.3.2跟踪 (10)2.3.3规则 (10)2.3.5其他 (13)2.4选项 (13)2.4.1同步 (13)2.4.2并行 (14)2.4.3其他 (15)2.5许可 (15)2.6日志 (17)第3章MOEBIUS集群部署 (18)3.1实时灾备模式 (18)3.1.1搭建和使用 (18)3.1.2数据切换 (19)3.2高可用模式 (21)3.2.1搭建和使用 (21)3.2.2故障转移 (21)3.3负载均衡模式 (23)3.4读写分离模式 (24)第4章集群使用的注意事项 (25)4.1用集群端口访问数据库 (25)4.2TEXT，NTEXT，IMAGE数据类型 (25)4.3SELECT INTO用法 (26)4.5导入导出工具 (26)4.6链接服务器 (27)4.7全文索引目录 (28)4.8大容量复制（B ULK C OPY） (28)4.9主外键的级联更新 (29)4.10批量更新主键 (29)4.11不支持W INDOWS帐户连接集群端口 (29)4.12不支持快照隔离级别 (30)4.13不支持MARS (30)4.14不支持事务保存点 (30)4.15不要修改数据库名称 (31)4.16使用INSTEAD OF表触发器 (31)4.17使用SP_RENAME存储过程 (31)4.18变化数据捕获（CDC） (31)第5章USP_MBS_CMD工具 (32)5.1检查唯一键 (32)5.2查找TRUNCATE TABLE用法 (33)5.3查找SELECT INTO用法 (33)5.4查找I NSTEAD OF触发器 (33)5.5拷贝登录名 (34)5.6并行执行 (34)5.8配置MSDTC (35)5.9配置防火墙 (35)5.10其他参数 (36)第6章集群的日常维护 (37)6.1修改连接属性 (37)6.1.1修改用户 (37)6.1.2修改IP地址 (40)6.1.3修改端口 (41)6.2环境升级 (42)6.2.1普通升级 (43)6.2.2滚动升级 (44)6.3仲裁文件夹故障 (44)6.4集群数据库的还原 (45)6.5集群数据库在线下使用 (46)第1章概要1.1致读者《Moebius for SQL Server用户手册》面向Moebius for SQL Server数据库集群的系统工程师、数据库管理员和日常运维人员。

moebius-for-sql-server安装部署手册

NO：Green Trend(DBC2012-JSWD-02)北京格瑞趋势科技有限公司Moebius for SQL Server安装部署手册© Copyright 北京格瑞趋势科技有限公司Corporation 2012. All rights reserved.目录第1章概要 (5)1.1致读者 (5)1.2文档结构 (5)1.3标记规则 (7)第2章安装环境准备 (8)2.1服务器 (8)2.2网络 (8)2.3操作系统 (8)2.3.1操作系统版本 (8)2.3.2区域与时间选项 (9)2.3.3系统时间 (9)2.3.4防火墙与杀毒软件 (9)2.3.5MSDTC服务 (9)2.4数据库 (9)2.4.1版本 (9)2.4.2SQL Server Management Studio (10)2.4.3数据库兼容级别 (10)2.4.4sa用户 (10)2.4.5系统库排序规则 (10)2.4.6SQL Server端口 (11)2.4.7SQL Server启动帐户 (11)2.4.8SQL Server内存分配 (12)第3章安装MOEBIUS配置管理器 (14)3.1安装环境 (14)3.2安装过程 (14)3.3安装后检查 (17)第4章搭建集群 (20)4.1添加首节点 (20)4.2为其它节点准备数据 (22)4.3添加其它节点 (22)第5章配置集群 (25)5.1配置集群端口 (25)5.2配置高可用 (26)5.2.1添加虚拟IP (26)5.2.2配置通知 (28)5.2.3配置监控 (30)第6章集群配置后步骤 (32)6.1检查数据库对象兼容性 (32)6.1.1TRUNCATE TABLE语句 (32)6.1.2SELECT INTO语句 (33)6.1.3INSTEAD OF触发器 (34)6.2同步登录用户 (34)6.3检查作业 (35)6.4其他 (35)第7章更新许可 (36)第8章卸载 (38)8.1删除节点 (38)8.2卸载管理工具 (38)8.3卸载M OEBIUS代理服务 (38)附件A：重装MS DTC服务与设置防火墙 (40)附件B：数据库兼容级别 (46)附件C：如何打开3GB选项 (47)附件D：手动安装MOE BIUS代理服务 (48)第1章概要1.1致读者《Moebius for SQL Server安装部署手册》面向初次安装配置Moebius for SQL Server数据库集群的系统工程师、数据库管理员和日常运维人员。

创建、部署和管理 SQL Server 虚拟设备说明书

Creating,Deploying,and Managing SQL Server VirtualAppliances Deploying SQL Server virtual appliances for Microsoft Hyper-V is oftenperceived as a complex and costly process.In this expert E-Guide,brought to you by SearchSQLServer .com and Dell,you will discover thebasic steps essential for effectively managing SQL Server virtual appliances.Learn why SQL Server database mirroring provides efficientprotection for today’svirtual databases.Explore how your businesses can effectively create and deploy SQL Server virtual appliances forHyper-V .E-Guide T echT arget Windows MediaCreating,Deploying,and Managing SQL Server Virtual Appliances Table of ContentsTable of Contents:Protect virtual databases through SQL Server database mirroring How to create SQL Server virtual appliances for Hyper-VDeploying a SQL Server virtual appliance for Microsoft Hyper-V Resources from Dell Inc,Microsoft and AMD Creating,Deploying,and Managing SQL Server Virtual AppliancesE-GuideProtect virtual databases through SQL Server database mirroringDanielle Ruest and Nelson Ruest,ContributorsVirtualizing applications like SQL Server can help an organization reduce costs.Furthermore,ever since Microsoft changed its SQL Server license model to a per CPU license model,it is possible to virtualize numerous instances of SQL Server on the same physical server.These licenses are costly,and therefore it is up to you to create a powerful host server that can run multiple virtual machines(VM)and SQL Server instances.Organizations often run several different types of SQL Server databases.For example,many management products come with run-time databases which are deemed operational,and can--and should--be consolidated into a central location to reduce the amount of locations SQL Server engines run.You may also have production databases —databases which are tied to internal applications–which are deemed informational databases.Other types of databases include financial,organizational,departmental and geographical.While each database is important to your organization,not all of them require the same level of protection.As a result,it's a good idea to use internal SQL Server features like database mirroring,a tool that provides protection for critical databases running in VMs(see Figure1).Figure1Database mirroring applies fault tolerance at the database level and automatically duplicates all of the contents of a database into another SQL Server installation.It will also automatically change over to the secondary database if the primary database is not available.The mirrored database can also be used to provide additional functionalities,like reporting services.You can even perform backups from the mirrored copy,avoiding any performance impacts on the production database. Since your databases have different protection requirements,you can use other,non-critical database engines from different VMs to protect important data.Furthermore,database mirroring does not require special hardware or software tools,as databases can be mirrored from one SQL Server VM to another.In the event of a host server failure--or even a VM failure--users are auto-matically redirected to the mirror database with little or no service interruption.If you decide to run database mirroring in your VMs,you should not make the virtual machines highly available through host server clustering.Otherwise the host cluster will restart the VM in the case of a failure.This could cause two versions of the same database to be live on the your network--something to avoid at all costs. Overall,features like database mirroring allow you to mix and match the types of databases you run in VMs.This lets you reduce costs while centralizing all of your SQL Server installations and providing protection for the databas-es that run your most critical data.Better Business intelligence at a Better price up to/SQLBIHow to create SQL Server virtual appliances for Hyper-V Danielle Ruest and Nelson Ruest,ContributorsThe ability to work with virtual appliances(VAP)or virtual machines(VM)that are pre-configured to run specific applications is one of the most impressive aspects of virtual infrastructures.To deploy an application--like SQL Server--into your network,all you need to do is generate a new VM from the source machine or appliance.There are two types of VAPs--commercial and mercial VAPs are generated by software manufacturers and can be downloaded from the manufacturer's website,while private VAPs are built in-house and are used for the organizations current applications.Commercial VAPs based on open source code are readily available from a variety of sources including the VMware VAP Marketplace.These VAPs come in Open Virtualization Format(OVF)and as a result,can be converted to almost any hypervisor environment.For example,you can use either Citrix'Project Kensho or Sun's xVM VirtualBox to convert a commercial VAP into Hyper-V format.On the other hand,when you need to work with operating systems that are not based on open source code,or when you want to work with a VAP for an application you already own,then you need to create private VAPs.This is the case for appliances based on Microsoft Windows Server,like SQL Server VAP.To deploy additional SQL Server VMs in your environment,you should create a private SQL Server VAP.This will reduce the time it takes to launch these machines.Start with a base VM,which ideally will be running Windows Server2008or Windows Server2008R2.These operating systems are enlightened guests in a Hyper-V environment.Also,consider using the Enterprise Edition because it supports the ability to create failover clusters and can scale more easily than the Standard Edition. The base VM should include the operating system,any required updates like Service Pack2for Windows Server 2008,and any required utility including management agents and/or anti-malware engines.Configure the base operating system according to your organization's standards.You may want to copy the VM since it can be used to create appliances running a multitude of other Microsoft Server applications like Internet Information Server,SharePoint Services or Office SharePoint Server,Commerce Server and more.Since the base virtual machine will be used for SQL Server,consider adding two additional disks to the VM.A larger disk can be used as the data disk while a smaller disk can be used as the disk storing the transaction logs. Once the base VM is ready,install SQL Server--ideally version2008or2008R2.First install all of the prerequi-sites for SQL Server,and then install SQL Server itself.Next,configure SQL Server to store data on the data disk—usually the D:drive—and the transaction logs on the log disk—usually the E:drive.Also perform any configuration modifications you need based on your organizational standards.Lastly,install any required updates for the SQL Server version.Your VM is now ready to turn into a VAP.Deploying a SQL Server virtual appliance for Microsoft Hyper-V Danielle Ruest and Nelson Ruest,ContributorsVirtual appliances(VAP)are fully configured virtual machines(VM)that include both an operating system and an application.As a result,they are one of the most powerful aspects of virtual infrastructures.Deploying a VAP is simple:create a copy of the VM and then configure it for pare that to the complexity of server application configurations and you will quickly warm up to using VAPs.For commercial applications like Microsoft SQL Server,a private VAP needs to be created.Downloadable,pre-config-ured VMs are not available because of licensing requirements for both the operating system(Windows Server)and the application itself.To create a private VAP,first generate a virtual machine,then install the operating system and lastly,install the application.This is a time-consuming process.Therefore,once the VAP is complete,create a copy of it to use as a backup.This will be useful when you need to install updates in the appliance.Typically,private VAPs targeted for Hyper-V environments include the following characteristics:•They are based on a custom VM that runs a copy of Windows Server2008Enterprise Edition.Windows Server2008is an enlightened guest operating system for Hyper-V and as a result,it will be fully integrated with the hypervisor.Also,the Enterprise Edition allows you to scale the VM more easily than other editions and install guest failover clustering,should you need it.•The machine includes any required patches or updates.It also includes any custom utility required foryour environment.•The machine includes at least three virtual disks:a system disk,a data disk and a logging disk.•The machine includes SQL Server(usually SQL Server2008)in the appropriate edition to meet yourneeds.It also includes a custom configuration for SQL Server--i.e.,data is stored on the data disk,logs are stored on the logging disk and other settings are modified--as well as the appropriate updates.•The machine has been depersonalized by the Sysprep utility.The last step,depersonalization,is required to eliminate the security identifier(SID)and other specific components of the VM,and it turns the VM into a VAP.In Windows Server2008,go to the%SystemRoot%\System32\Sysprep folder to launch Sysprep.exe(you'll need elevated rights to do so).Choose the following settings(see Figure1):•System Cleanup Action:Enter System Out-of-Box Experience(OOBE)•Select the Generalize checkbox•Shutdown Options:ShutdownFigure1.Preparing a virtual appliance with SysprepOnce the machine is shut down,you can use it to generate new virtual machines running SQL Server.Make sure you create a copy of this VM to use as a backup.The machine can then be stored in a Hyper-V source library.In order to create a new VM based on this VAP:1.Make sure the virtual machine is turned off.2.Locate the source files for the VM and copy them to a new location.Create a folder using the name ofthe VM and store the virtual disks in this folder.3.Generate a new virtual machine in Hyper-V and attach it to the copied disks.Assign appropriate RAM,network interface cards and other settings to the new VM.unch the new VM to generate a new security identifier,name it and join it to your production domain.5.Load the VM with production databases and start using it as a new machine in your infrastructure.This process is relatively simple,however,if you manage your Hyper-V environment with System Center Virtual Machine Manager(SCVMM),then you can automate the entire process(see Figure2)and have SCVMM both prepare the VAP and generate a new VM from the VAP template in a few easy steps.Figure2That's it-your SQL Server VAP is now ready for deployment.If you run virtual infrastructures and need to generate new VMs running the same applications,VAPs are the answer.Furthermore,you can--and should--create private VAPs of as many applications as possible since this will save you a lot of time when you need to deploy new machines.Creating,Deploying,and Managing SQL Server Virtual Appliances Resources from Dell Inc,Microsoft and AMDSponsored by:Page 11of11Resources from Dell Inc,Microsoft and AMDConsolidating SQL Server 2000Databases from Dell PowerEdge 2650Servers to a Dell PowerEdge R805ServerMoving SAP Off Mainframe to SQL Server Nets Australia’s QR Limited U.S.$100,000a Month ServiceU Achieves Outstanding Power Savings and Performance ImprovementsAbout Dell Inc,Microsoft and AMD:Together –Dell,AMD and Microsoft are working to provide our customers with solutions for line of business applica-tions,collaboration and business intelligence.Powered by AMD Opteron™Processors,Dell PowerEdge 2and 4socket servers loaded with Microsoft's SQL Server 2008and Windows Server 2008,deliver best in industry performance.They run cooler ,and deliver benchmark setting throughput that meets,and often exceeds,the demands of businessusers.With the added capability of Dell Professional Services to assist with SQL Server ,Data Warehousing and Business Intelligence,Dell is a single source for Database and BIsolutions.。

1、下载文档前请自行甄别文档内容的完整性，平台不提供额外的编辑、内容补充、找答案等附加服务。
2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
3、如文档侵犯您的权益，请联系客服反馈,我们会尽快为您处理(人工客服工作时间：9:00-18:30)。

本文档的目的是指导用户快速完整的安装和配置Moebius集群。

关于Moebius集群的使用和技术细节，请参考《Moebius for SQL Server用户手册》和《Moebius for SQL Server技术白皮书》。

1.2文档结构本文共分8章，从第2章开始按照软件的使用流程，详细介绍了它的安装配置步骤。

图1：安装部署结构图具体内容包括以下几个部分：●第2章“安装环境准备”环境准备是安装Moebius集群的基础，请仔细检查您的系统环境，以便安装和搭建过程能够顺利的进行。

●第3章“安装Moebius配置管理器”该部分内容介绍了Moebius配置管理器的用法，对配置管理器和数据库集群的区别做了介绍。

●第4章“搭建集群”该部分主要介绍Moebius标准集群的搭建过程。

●第5章“配置集群”在集群节点搭建成功后，必须对集群做相应的配置之后，才能充分使用集群的所有功能。

包括虚拟IP的设置、通知和监控的配置以及Moebius集群端口的配置等。

文中提到的“节点”，在没有特别说明的情况下都可以理解为“服务器”。

●第6章“集群配置后步骤”用户在使用Moebius集群过程中遇到的很多问题都是由于没有正确的完成这部分操作导致的。

该部分内容包括修改部分不符合集群规范的SQL语句，集群中作业的使用等。

●第6章“更新许可”Moebius数据库集群的许可为每个数据库一个，该部分介绍如何获取授权码和更新许可。

●第7章“卸载”●附录该部分为安装配置过程中某些操作步骤的详细说明和运行脚本。

1.3标记规则的内容表示注意事项，标记的内容为某些操作方法的提示，标记的内容为安装配置过程中的常见问题。

文中出现的代码和脚本都记录在灰色的脚本框中。

如果没有特殊说明，本文使用的都是SQL Server 2008的截图和示例。

第2章安装环境准备2.1服务器安装部署Moebius for SQL Server数据库集群，至少需要两台服务器。

若集群中配置了高可用，建议两台服务器的配置相当。

否则，计算能力较好的服务器发生故障，自动故障转移后，计算能力较弱的服务器无法支撑业务。

首节点即第一个加入到集群的节点，见第四章：搭建集群2.2网络集群中各节点是通过网络来交互数据的，确保集群各节点网络物理连接可靠、稳定；确保相互之间的IP地址和机器名都能够ping通。

要求ping通相互的机器名，是为了保障Windows分布式事务的正常使用。

可以在CMD窗口中使用hostname命令来查看机器名。

如果能ping通IP地址但是ping不通机器名，可以修改”C:\Windows\System32\Drivers\etc\hosts”，然后就可以ping通了。

2.3操作系统2.3.1操作系统版本集群对操作系统的版本没有具体要求，只要能顺利安装SQL Server数据库即可。

建议生产用操作系统为服务器版：Windows 2000 Professional/Server/Advanced Server/Datacenter ServerWindows Server 2003 Standard/Enterprise/DatacenterWindows Server 2008 Standard/Enterprise/Data CenterWindows Server 2008 R2从有效利用内存角度出发，建议用户使用64位操作系统。

2.3.2区域与时间选项确认各个节点上的"区域与时间选项"设置一致。

这些选项包括时间和日期格式，字符编码等。

如果是中文的用户，建议在安装微软的SQL Server数据库之前就把这些选项设置好。

2.3.3系统时间检查集群各节点的系统时间，若不一致将其调整统一，Moebius集群在多个地方要用到系统时间，如记录集群日志等。

2.3.4防火墙与杀毒软件如果操作系统启用了防火墙，请将MSDTC服务配置成例外。

具体方法参考附件A。

如果安装了杀毒软件，在安装集群过程中，可能会提示“是否允许…”等信息，请选择“允许”。

2.3.5MSDTC服务该服务是Windows自带的分布式事务协调器。

在搭建集群之前要确保该服务已启动且工作正常。

该服务在Windows服务列表中的名称为“Distributed Transaction Coordinator”，建议将其设置为自动启动或自动（延时）启动。

如果您的操做系统是克隆的，系统的"Distrabuted Transaction Coordinator"服务（MSDTC 服务）的CID可能会有冲突，需要在冲突节点上重新安装MSDTC服务。

具体方法见附件A。

2.4数据库2.4.1版本Moebius for SQL Server数据库集群支持以下数据库版本：SQL Server 2005 Standard/Enterprise SP2以上SQL Server2008 Standard/EnterpriseSQL Server 2008 R2 Standard/Enterprise2.4.2 SQL Server Management Studio在安装Moebius 配置管理器的环境中，必须已经安装了SQL Server Management Studio 。

见第三章：安装Moebius 配置管理器。

2.4.3 数据库兼容级别Moebius 数据库集群只支持90以上的兼容级别。

如果数据库是从SQL Server 2000升级的，需要把兼容级别调到90以上，并且确保数据库在该级别能够正确的使用。

2.4.4 sa 用户在搭建集群之前，应该将SQL Server 的认证模式设置为混合模式。

在添加节点的过程中SQL Server 必须存在sa 用户。

2.4.5 系统库排序规则在搭建数据库集群之前应该检查系统库的排序规则。

在中文简体操作系统上安装SQL Server 数据库，默认的排序规则为Chinese_PRC_CI_AS 。

建议将系统数据库的排序规则改为Chinese_PRC_CI_AS 。

问：公司的安全策略规定不能使用sa 用户怎么办？答：只需要存在该用户即可，可以将sa 设为“禁用”。

并且在成功搭建集群后，就不需要sa 用户了。

关于数据库兼容级别的更多信息，请见附件B 。

可以通过下面的语句查看数据库兼容级别SELECT compatibility_levelFROM sys.databases WHERE name = 'DB_NAME';2.4.6SQL Server端口搭建Moebius集群要求各个节点上的SQL Server实例使用静态端口。

在SQL Server配置管理器中，选择“SQL Server 2008 网络配置”- “MSSQLSERVER 的协议”- “TCP/IP”，在“IP All”- “TCP 端口”中检查或指定该静态端口。

更改后需要重新启动SQL Server服务。

2.4.7SQL Server启动帐户搭建Moebius集群要求运行各个节点上的SQL Server实例的用户要有Local System的权限。

在SQL Server配置管理器中，选择“SQL Server 2008 服务”，在右侧的主窗口中选择数据库实例对应可以通过下面的语句查看数据库排序规则SELECT [name], [collision_name]FROM sys.databases的服务，右键点击并选择属性，在登录页中更改帐户。

如果是内置账户，请选择“Local System”，如果是本账户，请确保输入的账户有Local System所拥有的权限。

更改后需要重新启动SQL Server 服务。

使用本地账户时，要确保该账户有修改注册表和读写本地文件的权限。

2.4.8SQL Server内存分配如果您使用的是64位操作系统，请跳过这一步。

否则，在SQL Server配置管理器中，选择“SQL Server 2008 服务”，在右侧的主窗口中选择数据库实例对应的服务，右键点击并选择属性。

在属性对话框中选择“高级”页，并在“启动参数的最后加上“；-g1024”。