The Configuration tab lets you specify the audit table to exclude, the default architecture profile, the database list, in which cases to save the project changes, and how many recent files to display in File Menu.
For information about any button in the Options dialog, click here.
Since you don't want to audit your Audit tables this option provides a convenient way to exclude them from the table grid on the main interface. It works by prefix so if you have a common prefix for all of your Audit structure tables like "AUDIT*" then entering this keyword in this text box will effectively exclude these tables.
This option will tell ApexSQL Audit to look for the Audit Architecture Profile File indicated in this field. If no file path is provided it will look for it in the application path. This saves the users from having to locate and open this file every time they use ApexSQL Audit. Loading the Audit Profile is a pre-requisite to most operations.
These options determine when the user is prompted to save a project, one that has unsaved changes. Various application events are listed that can be used as events to prompt for project save.
You can choose how many projects you created or opened to be displayed in the File Menu. The maximum number is 15. For example, if the maximum number is 6 then the last 6 projects are in the list.
The Show default owner/schema Qualification in common interface labels option (disabled by default) changes names by standard. If it is enabled, then object names in common interface labels are shown in regular way. For example [dbo].[royalper] appears just the same.
If it is disabled, then the following rules are applied:
If the object belongs to dbo owner/schema then the owner/schema is not shown. Otherwise the owner/schema is shown.
If there are no spaces or special characters (not alphanumeric ones) in the object name (schema/owner) then the object name should not be enclosed in brackets. If the object name (schema/owner) has such special characters then it should be enclosed in brackets.
Taking the rules above into consideration we get the following:
[dbo].[royalper] appears as royalper
[brian].[royalper] appears as brian.royalper
[dbo].[royal per] appears as [royal per]
[brian].[royal per] appears as brian.[royal per]
[brian lockwood].[royal per] appears the same
Copyright © 2008 ApexSQL LLC. All Rights Reserved.