Topic Last Modified: 2011-02-03
Archiving Server requires a supported 64-bit edition of the Microsoft SQL Server database software to store the archive data. You can either select a previously defined SQL store to be used for archiving or define a new SQL store by specifying a fully qualified domain name (FQDN) of the server on which the SQL store is to reside and the SQL Server instance you want to use for the new SQL store (which can be the default instance or a named instance that you specify).
For details about SQL Server support, see Database Software and Clustering Support in the Supportability documentation. For details about the archiving database, including collocation of the archiving database, see Supported Server Collocation in the Supportability documentation, Components and Topologies for Archiving in the Planning documentation, Components and Topologies for Archiving in the Planning documentation, SQL Server Data and Log File Placement in the Deployment documentation, and Installing SQL Server for the Archiving Database in the Deployment documentation.
|If the account used to publish the topology has the appropriate
user rights and permissions, you can create the archiving database
(LcsLog) when you publish your topology. You can also create the
database later, including as part of the installation
To install and deploy the databases on the SQL Server-based server for archiving, you must be a member of the SQL Server sysadmins group for the SQL Server-based server where you are installing the database files. If you are not a member of the SQL Server sysadmins group, you must request that you be added to the group until the database files are deployed. If you cannot be made a member of the sysadmins group, you should provide your SQL Server database administrator with the script to configure and deploy the databases. For details about the proper user rights and permissions that you need to accomplish the procedures, see Deployment Permissions for SQL Server in the Deployment documentation.