It can be very helpful to check the consolidated database tables on your Sybase Unwired Platform server during MBO development and testing. Possible reasons why one might want to check the CDB: * For MBO operations where the Cache Update Policy checkbox “Apply results to cache” is checked, verify that the changes or results from the backend are really applied to the CDB. * During DCN development and testing, verify that the DCN functionality is working or to determine the DCN data string to be passed. For instance, I was able to see what date string the CDB was expecting by looking at other records in the CDB. All of the above can also been accomplished by setting the right traces and by checking the generated log files. However, being able to look at the actual CDB table might be easier and gives me personnally more confidence than checking a log file. Simplified, every MBO is mapped to one CDB table for its data (there are administrative tables too). It is recommended to keep package names characters and MBO names short (package names 4 to 6 characters) or at least to make sure that MBO names are different from one another in the first few characters (as opposed to having long generel prefixes). This will make it easier to identify the CDB table corresponding to a given MBO. Disclaimer: 0.1. Do not to change any data on the CDB directly through the DB connection that we are going to set up. 0.2. Do not use this in a productive system. This is for devepment and testing. 0.3. Keep the connections to the CDB short and don’t deploy packages or perform any other administrative tasks while the connection is open (I heard of a case where the SUP server would not start up again after someone redeployed a package while a connection to the CDB from the Sybase Unwired Workspace (SUW) was still open.) 1) First take note of the CDB configuration in SCC.2) In SUW->Enterprise Explorer, create a new database connection. In the wizard pick connection type Sybase ASA. Enter a name for the connection, then press Next.3) Enter the connection properties previously determined in SCC. Note that you can leave the dba user name and password as it is defaulted provided that your SUP installation is a default development installation. Note that the default password for user dba is empty (despite the “***” displayed). Press Finish.