The following are assumptions and requirements that need to be met before you continue installing Workbench:
Microsoft Products Required
SQL server has been installed on a server inside your network
Available on the network (either on the Server or a network workstation) is a full working version of Microsoft Access.
Technical User Setup Skills Required
The person doing the installation has:
-
- a working knowledge of the network.
- a working knowledge of Active Directory.
- a working knowledge of SQL Server Studio Manager
- is able to backup and restore SQL Server databases
Technical Setup in Place
In Windows Active Directory you must have created a User Group called Workbench_Users. This user group will be used to grant access rights to the SQL database/s that are described later in this document
All the users with logins in Active Directory who will need to use Workbench must have been put in this Group. You may want to create more than one user group if there will be different users for different Workbench instances.
On the server that has SQL server installed a directory called Workbench must have been created.
Share this directory (and all its sub directories) and allocate full control rights to the Workbench_Users Group. This directory will be used to store all the files needed to create and run Workbench.
This install document is based on the 2005 Microsoft SQL Server, Workbench will work with both 2000 and 2008 versions but the installing instructions will differ from these contact Workbench International if you require further details. Please note that Workbench International recommend that all service packs be applied before installation.
Rights to Master Database
Some export processes require user rights over the xp_cmdshell stored procedure in the Master database, either directly or via proxy.
Follow this link on how to setup a proxy account for xp_cmdshell
http://msdn.microsoft.com/en-us/library/ms190359.aspx