New queries assigned to process on Node %1!s! have not been picked up by a worker thread in the last %2!s! seconds. Blocking or long-running queries can contribute to this condition, and may degrade client response time. Use the "max worker threads" configuration option to increase number of allowable threads, or optimize current running queries. SQL Process Utilization: %3!s!%%. System Idle: %4!s!%%.
New input file was selected. You can keep or reset the existing metadata. Click Yes to keep the existing column metadata. ...
New parallel operation cannot be started due to too many parallel operations executing at this time. Use the "max worker ...
New Publication Wizard must configure '{0}' as a Distributor before automatically generating filters for this publication. ...
New Publication Wizard must configure '{0}' as a Distributor before you can add an Oracle Publisher. Do you want to configure ...
New queries assigned to process on Node %1!s! have not been picked up by a worker thread in the last %2!s! seconds. Blocking ...
New re-publishing identity range pool was allocated to subscriber for article %1 with values range_begin = %2, range_end ...
New sort run starting on page %1!s! found an extent not marked as shared. Retry the transaction. If the problem persists, ...
New subscriber identity range was allocated to subscriber for article %1 with values range_begin = %2, range_end = %3, next_range_begin ...
Next steps: - To configure each source, double-click the source. - To indicate the flow of data, drag the green output arrows ...