Examples with "of changes are automatically captured" and their translation in Japans
We konden deze vermelding niet vinden. Er worden benaderende resultaten weergegeven. Controleer je spelling of stel voor deze term aan het woordenboek toe te voegen.
HomeBase starts by creating production server configuration profiles on a scheduled basis ensuring the smallest of changes are automatically captured.
Product change histories are automatically captured and recorded as part of the product development, further building out the product's Digital Thread.
With implicit capture, data definition language (DDL) and data manipulation language (DML) changes are captured automatically either by a capture process or by synchronous capture. A specific type of message called logical change record (LCR) describes these database changes. Both a capture process and synchronous capture can filter database changes with user-defined rules. Therefore, only changes to specified objects are captured.
When a database object is prepared for instantiation at a source database, an Oracle Streams data dictionary is populated automatically at the database where changes to the object are captured by a capture process. The Oracle Streams data dictionary is a multiversioned copy of some of the information in the primary data dictionary at a source Oracle Streams data dictionary maps object numbers, object version information, and internal column numbers from the source database into table names, column names, and column data types. This mapping keeps each captured LCR as small as possible because a captured LCR can often use numbers rather than names internally.
Versioning is a method to capture changes and updates made to any transaction, that includes sales orders, quotes, and Sales Agreements. Creating and managing versions can be of great assistance during the negotiation phase of any transaction and helpful when maintaining history throughout the life of a sales order, quotes, and Sales Agreement. The history of changes that are made to a transaction are captured and stored, available to be viewed and compared later. Depending on the set up in the Processing Constraint Framework, changes can automatically trigger versioning or you can choose to manually version the transaction.
Orders entered before the Gross Margin feature is installed or enabled will not have costs captured and thus will not have margin visible. If you want to obtain costs for such lines or orders, you can use the Get Cost action. Costs are automatically refreshed on unshipped order lines when attributes affecting the cost (warehouse and project) change. But if you know the cost has changed in Oracle Costing, you can manually obtain a more current cost by using the Get Cost action. Cost is frozen on the order line at the time of shipping.
If you turn forwarding on after it has been off, then RepliStor automatically forwards to the target system all I/O changes captured and stored while forwarding was off.
Two or more databases contain shared database objects. When a change is made to a database object at one database, the change is automatically captured, propagated to the other databases, and applied at the other databases.
If not set, a new frame will be captured each time the canvas changes; if set to 0, frames will not be captured automatically; instead, they will only be captured when the returned track's requestFrame() method is called.
Implicit capture means that database changes are captured automatically and enqueued them. Implicit capture can be accomplished with a capture process or with a synchronous capture. A capture process captures changes in the redo log, while a synchronous capture captures DML changes with an internal mechanism. Both capture processes and synchronous captures reformat the captured changes into logical change records (LCRs) and enqueue the LCRs into an ANYDATA queue.
Wait until the apply process that applies changes that were captured by the capture process has reached the SCN specified in Step 13. When this event occurs, the apply process is automatically disabled with error ORA-26717 to indicate the SCN limit has reached.
With implicit consumption, an apply process automatically dequeues either captured LCRs, persistent LCRs, or persistent user messages. The queue must be an ANYDATA queue. If a message contains a logical change record (LCR), then the apply process can either apply it directly or call a user-specified procedure for processing. If the message does not contain an LCR, then the apply process can invoke a user-specified procedure called a message handler to process it.
Once you have captured a SQL workload that you want to analyze into a SQL tuning set, you can run SQL Performance Analyzer to analyze the effects of a system change on SQL performance. To run SQL Performance Analyzer, you must first create a SQL Performance Analyzer task. A task is a container that encapsulates all of the data about a complete SQL Performance Analyzer analysis. A SQL Performance Analyzer analysis comprises of at least two SQL trials and a comparison. A SQL trial captures the execution performance of a SQL tuning set under specific environmental conditions and can be generated automatically using SQL Performance Analyzer by one of the following methods
Er worden alleen voorbeelden gegeven om u te helpen het woord of de woordcombinatie waarop u hebt gezocht, te vertalen. Deze worden niet door ons geselecteerd of gevalideerd en kunnen ongepaste taal bevatten. Wij vragen u melding te maken van voorbeelden die dienen te worden aangepast of verwijderd. Vertalingen met grof of informeel taalgebruik worden meestal rood of oranje gemarkeerd.