Within ArcGIS software, the term database servers refers to instances of Microsoft SQL Server Express that have been enabled to store desktop or workgroup geodatabases.
You create geodatabases and perform other administrative tasks for database servers through the Database Servers node in the Catalog window or ArcCatalog. Performing the administration of the database server and its geodatabases through ArcGIS for Desktop means there is no extra software or database administration expertise required for you to create and use these types of geodatabases.
To get started using database servers, this tutorial will show you how to use ArcGIS for Desktop to do the following:
- Add a database server and create new geodatabases.
- Add users to the database server and grant permissions.
- Load data into the geodatabases.
- Make edits to data in a geodatabase on a database server.
- Perform administrative tasks, such as making a backup of and upgrading a geodatabase.
You can complete this tutorial at your own pace. This tutorial includes ten exercises, each of which takes between 10 and 30 minutes to complete. Exercises are cumulative; you must complete them in order.
To complete the tasks in this tutorial, you must install ArcGIS for Desktop, the SQL Server Native client, Microsoft SQL Server Express, and the tutorial data. You must also create additional logins on your computer to complete some of the tasks.
You must install ArcGIS for Desktop (Standard or Advanced license level), the SQL Server Native Client, SQL Server Express, and the ArcTutor data for this tutorial on your computer. Use the Database Servers Installation wizard provided with the ArcGIS for Desktop setups to install an instance of SQL Server Express and enable it to store geodatabases. To complete the installation, follow the instructions in the Database Servers installation guide, which is also included with the ArcGIS for Desktop setups.
You can download the SQL Server Native Client from My Esri or from Microsoft's website. Be sure to download the correct client for the release of SQL Server Express you are installing. The SQL Server Native Client must be installed on the computer where ArcGIS for Desktop is installed so you can connect to the SQL Server instance. Follow Microsoft's instructions for installing the SQL Server Native Client.
You most likely already have ArcGIS for Desktop installed, but if not, follow the instructions in the ArcGIS for Desktop installation guide to complete this. If the ArcTutor data has not been installed, you need to install it using the ArcTutor executable provided with the ArcGIS for Desktop setup.
As with all software installations on Windows operating systems, you must be an administrator on the computer to install SQL Server Express, the SQL Server Native Client, ArcGIS for Desktop, and the tutorial data. If you do not have administrative rights to the computer you are going to use for this tutorial, have your systems administrator install the software. Be sure the system administrator adds your login to the SQL Server Express instance as a database server administrator when he or she enables the SQL Server Express instance to store geodatabases.
The database server administrator is responsible for maintaining the database server, creating and maintaining geodatabases, and adding and administering their database server user accounts. This tutorial shows you how to perform these tasks; therefore, without database server administrator permissions, you could not complete this tutorial.
Database servers use Windows-authenticated logins for authentication exclusively. This tutorial requires four Windows logins: your login and three others.
If you are an administrator on your computer, you can create local Windows logins and use those. If you are not an administrator, have your systems administrator either add three users to your computer or provide you with three network logins to use.
You will use these logins to learn how to do the following:
- Add other users to your database server and grant them permission to the geodatabase and the data it holds.
- Assess what the different levels of permission allow or prevent users from doing so you can decide what sort of permissions you should grant to other users.
- Use the database server and its contents as a nonadministrative user. Therefore, if you connect to a colleague’s database server on which you have restricted permission, you will know how to use it.
- Keep track of who has been editing a feature class and when.