Monthly Archives: December 2009
Hello, this is Sigmund Frodo…er…Jim W., Geodata Analyst at ESRI Support Services in Charlotte, NC with some thoughts that might help to ‘enlighten’ you on the inner life of your relational database management system (RDBMS). Just as some humans will visit a psychiatrist to help them understand the inner workings of their minds, databases have been known to benefit from the help of a qualified professional practitioner who can give meaning to the vast number of disassociated bits and bytes that swirl around deep within their digital brains. Regular ‘analysis’ of a database can be a good thing and can help to maintain an optimum level of equilibrium necessary for quickly answering the ‘BIG’ queries of life, such as, “Where can I find a good burger?”
Now, geodatabases have been known to have a ‘spatial’ complex, and periodically analyzing them will keep them grounded in reality, thereby improving overall performance. But first, we digress with a brief interlude into the realm of statistics…
Analyzing a database involves collecting statistics that help us to get a handle on the nature of the data that is contained within the database. These statistical facts about objects such as tables, columns, and indexes are then stored internally within the RDBMS’s data dictionary tables. They help the database optimizer to determine the optimum path to data, ensuring the fastest response time for queries, while at the same time minimizing the cost of database resources. For example, getting a count of how many rows of data are contained in each table may help the database optimizer determine whether or not to use an index, or how best to join two tables when selecting the best execution plan for a given SQL statement.
What kinds of statistics are gathered? Analyzing a table can retrieve and store metadata such as the number of rows in each table, the average row length in bytes, the average column length, the minimum and maximum values contained in each column, and the number of null values in a column. Other statistics can describe the data by looking at the number of distinct values contained in a column (known as its cardinality), as well as by constructing histograms that give an idea of how the data is distributed (whether the data is evenly distributed throughout its range, or is it clumped together with a large number of rows containing similar values). Clinical terms such as platykurtosis, leptokurtosis, and skewness come fondly to mind, but that’s another story for another time…
So, you may ask, “Just how are statistics collected?” It can be as simple as pointing and clicking on an individual feature class in ArcCatalog and then analyzing. You could also use an ArcSDE command line tool called sdetable, or the Analyze geoprocessing tool available in ArcToolbox. Or, you might even want to set up an automated scheduled task using the tools to gather statistics provided by the specific RDBMS that you’re using.
For a more in-depth look at analyzing a geodatabase and collecting statistics, most of what you’ll need to get started is located at: About updating geodatabase statistics.
Just remember, since data can be dynamic and ever changing, it’s a good idea to frequently analyze in order to pick up any changes that may occur in the database. In a healthy geodatabase, where numerous edits may occur on a daily basis, it could be wise to schedule frequent analysis sessions. Regular analysis can help improve the display time of versioned feature classes, as well as speed up other edit processes where fast query response times are required to keep you from waiting. And best of all, there’s no charge!
- Jim W., Support Analyst – Geodata Unit, ESRI Support Services, Charlotte, NC.
PATCH Released to fix the issue of Raster Catalogs and Feature Classes with Raster Fields stored in ArcSDE for SQL Server not displaying in ArcMap after installing ArcSDE 9.3.1 SP1
In a previous blog post, we stated that several users were calling into ESRI reporting an issue that Raster Catalogs and Feature Classes with Raster Fields stored in ArcSDE for SQL Server do not display after applying the 9.3.1 Service Pack 1.
There is now a patch available that resolves this issue: ArcSDE 9.3.1 SP1 SQL Server Raster Catalog and Raster Field Patch.
This patch fixes the following bugs:
· NIM052174 – Raster Catalogs and Feature Classes with raster fields stored in ArcSDE for SQL Server do not display after applying the 9.3.1 Service Pack 1.
ESRI apologizes for any inconvenience this may have caused you. If you have any issues installing the patch, please contact ESRI Support Services.
-Eric R., Development Tech Lead – UAG, ESRI Support Services
Viewership on the Support Center News (SCN) blog has steadily increased over the past year. I wanted to take a moment to say “Thank You” for coming to the SCN blog for whatever reason you may be visiting or browsing.
Last year, an ESRI Support Analyst, Emeline R., wrote a humorous piece associated with GIS and the holiday spirit. I wanted to share that post with everyone again this year with the hope that those of you who might have read it last year will, once again, find the humor in it, and those of you who are new to the SCN blog can enjoy it for the first time.
HAPPY HOLIDAYS FROM ESRI SUPPORT SERVICES!
- Collin W., SCN blog content manager, ESRI Support Services
Working in Support Services here at ESRI, we never know what kinds of incidents may come our way. With the Holidays approaching, we received an incident that we thought you, our users, might find interesting:
We go into production December 24th and our Mobile Applications still won’t work! We made a map using our North_Pole.ttf font on joined parcel data filtered by “LANDUSE=’Residential’”, and symbolized by the YOUVEBEEN field. We are using the Streets Network Dataset from the ESRI Data & Maps CDs to create the optimal route between these features. Using a domain STOPLENGTH and the subtype YOUVEBEEN field (because Coal only requires a three second stop), we finally got the Route all set up in ArcMap. But as soon as we publish to ArcGIS Server, we lose the special symbols from the North_pole.ttf file. Organizational policies restrict us to use only this font to symbolize our maps!
We’ve got the mobile service uploaded to our Trimble Bells 500x, but we can’t get the network data to respond to the GPS on the device. Bill Donner and Rosie Blitzen, our IT admins, won’t grant me administrative rights and Don Comet & Ella Cupid insist that nothing will replace a good old fashioned nose!
If you can get this fixed, there’s some cookies and milk in it for you!
Rudolph T. R. N. Reindeer
90* 00’ 00” N
We, at ESRI Support Services wish you a wonderful holiday season! And we hope that our help allowed Rudolph and Santa to get to you and make all your holiday wishes come true!
Several users have called in to ESRI Support Services in the last few days and reported the following issue: after installing ArcGIS Desktop 9.3.1 Service Pack 1 when direct connections are used or after installing ArcSDE 9.3.1 Service Pack 1 when application server connections are used, Raster catalogs are not displaying in ArcMap. This issue also impacts Raster Fields stored in Microsoft SQL Server. If you have Raster fields on your feature class, you will not be able to access that information after applying 9.3.1 Service Pack 1.
ESRI is aware of this issue, and is currently working on a resolution to this problem. We appreciate your patience and understanding, and are sorry for any inconvenience this may have caused you.
The following Bug reports are currently being investigated for a possible solution:
- NIM052174: ArcSDE Raster catalogs do not display using ArcMap 9.3.1 Service Pack 1
If you have not installed ArcSDE 9.3.1 Service Pack 1, please wait to install it until this issue has been resolved.
For further information, please refer to knowledge base article 37463.
We will keep you posted via this blog post for further updates as they become available.
- Eric R., Development Tech Lead – User Advocacy Group, ESRI Support Services
When creating an Online Support Incident, it is often cumbersome to fully document exactly what you are doing. Whether you don’t know the correct terminology or don’t feel like sending an e-mail that rivals epic novels such as War and Peace and Horton Hears a Who!, the Problems Steps Recorder is here to help you. This very helpful feature was added to the Windows 7 operating system and will soon become your best friend!
To open the Problems Steps Recorder, follow the steps below:
1. Click on the ‘Start’ button.
2. In the search dialog type ‘psr’ and press ‘Enter’.
Launching the psr.exe opens a new toolbar that appears on the desktop.
This easy-to-use tool allows you to begin recording screen shots as soon as you click ‘Start Record’. Once the recording has begun, navigate through the issue you would like to report. When you are done, click ‘Stop Record’ on the Problem Steps Recorder toolbar. After clicking the ‘Stop Record’ button on the toolbar, you will be prompted to name the .zip file that will contain your screen captures. The next step will be to include this .zip file when you create your new ESRI Support Services request online.
*Note there is a 10 megabyte file size limitation on uploads. If the file is larger than 10 MB, simply ask the Support Analyst you work with for instructions on using the FTP site.
- Andrew S., Server Support Analyst, ESRI Support Services
We are pleased to announce that ArcGIS 9.3.1 Service Pack 1 was released today. With Service Pack 1 now available, there is an accompanying list of the issues that were addressed within the new service pack. You can check out the entire list by going to the Issues addressed with Service Pack 1 Webpage on the ESRI Support Center Web site. Many of these issues came directly from customers reporting them to ESRI Support Services and were prioritized to be included in this service pack.
For details on each individual product’s service pack, the issues addressed, instructions on how to install the service pack and other information, see each product’s link below:
If you run into any issues with the installation of this service pack or have feedback, please contact ESRI Technical Support at 1-888-377-4575. International sites, please contact your local ESRI software distributor.
- Collin W., SCN Blog Content manager, ESRI Support Services
Merriam-Webster defines community as “a body of individuals organized into a unit or manifesting usually with awareness some unifying trait”.
With this definition in mind, it can be said that wiki.GIS.com is developing a community. Our “unifying trait” is GIS or knowledge and awareness of GIS and its many uses.
With an increase in users comes the creation and editing of wiki pages. By looking at the recent changes to wiki.GIS.com, you can see that the creation and editing processes have involved some collaboration amongst users. Collaboration and a wiki go hand-in-hand, so it is good to see a community formulating and collaborating within wiki.GIS.com.
Upon the launch of wiki.GIS.com, GIS Lounge posted a blog with an approximation of the number of content pages at that time and an invite to add your knowledge of GIS to wiki.GIS.com. It is always great to see the community get involved with spreading the word and creating some chatter.
Since the launch of wiki.GIS.com there have been about 75 content pages added and a few new users are creating accounts every day. As I have found out through browsing, adding to and editing the wiki, it can be fun and it is always a learning experience. Jump in head first and see what or how you can contribute to wiki.GIS.com.
- Collin W., SCN Blog Content manager, ESRI Support Services
Emeline here again with a heads-up about the changes coming to the ESRI Support Services phone-routing system. In the past, have you ever
- had to wait on the phone a long time before being able to speak to an analyst,
- been repeatedly asked the same questions about the issues you are encountering and the products you are using, and/or
- had your call transferred to several analysts before reaching the best person to help you?
Our new phone routing system utilizes Computer Telephony Integration (CTI) and will help resolve a lot of these problems. Here’s the deal: When you call ESRI Support Services (ESS), you will be asked for your customer number and the last four digits of the telephone number ESS has on file for you. If you are unsure of what information we have on file for you, do not worry. Our Support Services receptionists will still be here to assist you through the process the next time you need to contact us for support. Next, you’ll be presented with a phone tree that is designed to direct your incident to the most appropriate Support team in three prompts. The first menu will ask you about which product you are using, such as ArcGIS Desktop and Extensions, ArcSDE, ArcGIS Server, ArcIMS, or Other. Then, a second menu will ask you about the general area in which you are experiencing a problem. A third menu may ask you for more details about the problem, or a more specific question about the area you specified in the second menu.
Say, for example, you are having trouble with the behavior of the Maplex labeling engine in ArcMap. In the first menu, you would answer ArcGIS Desktop, since ArcMap, as well as ArcCatalog, are part of this product. In the second menu, you would select ArcGIS Extensions, since you are working with a particular extension. In the third menu, you would select the choice for the Maplex extension.
Here’s another example: You’re a developer working on a .NET ADF Web application for ArcGIS Server, and you’ve hit a road block with your code. In the first menu, you would select ArcGIS Server. The second menu will ask whether you are making a custom application for ArcGIS Server. In the third menu, you will be asked about the ADF or API you are using, so you would select the choice for .NET.
These are just a couple simple examples. Once you call in a couple of times, you’ll know the first menu by heart, since there will only be a few options. Also, there will always be the option to talk to one of our Support Services receptionists in case the system doesn’t provide the correct area for the problem you are encountering. Our phone tree is designed to sort your incident to the most appropriate Support analyst in three prompts. This analyst will collect your system information, summarize the issue, and help start you on the path to resolving the issue!
- Emeline R., Support Analyst, ArcGIS Server group, ESRI Support Services