This article offers initial theorizing on an understudied phenomenon in the workplace: the meeting after the meeting (MATM).
Combined, results suggest that the polite, ritualistic, and formulaic nature of small talk is often uplifting yet also distracting. Our results also showed higher levels of trait-level self-monitoring mitigated the negative effects of small talk on work engagement. Using multilevel path analysis, our results showed that, on one hand, small talk enhanced employees’ daily positive social emotions at work, which translated into heightened organizational citizenship behaviors (OCB) and greater well-being at the end of the workday on the other hand, small talk disrupted employees’ ability to cognitively engage in their work, which compromised their OCB. Given that we are the first to examine small talk as an episodic phenomenon, we also conducted a scale validation of our daily small talk measure with Masters students from a University in the Northeastern US (n = 73) and two samples of employed adults registered with Amazon Mechanical Turk (n = 180 and n = 202). In a sample of employed adults recruited from a Northeast US University’s alumni database and LinkedIn (n = 151), we used an experience sampling method (ESM) to capture within-individual variation in small talk over a three-week period. Integrating theories of interaction rituals and micro-role transitions, we explore how and why seemingly inconsequential conversations during the workday generate meaningful effects on employees’ experiences. Yet, emerging research suggests small talk may have important consequences for employees. Although small talk comprises up to one-third of adults’ speech, its effects in the workplace have been largely discounted. Even if we had an index on Name column, the index wouldn’t be used because of the implicit conversion on the column.Small talk-short, superficial, or trivial communication not core to task completion-is normative and ubiquitous in organizational life. The QO cannot use clustered index seek because of the OR operator. Sidenote: the query below will fail due to conversion error (the order of the predicates is irrelevant). Test2 again shows that we the sequence of predicate evaluation is controlled by QO and is not short-circuited.
It simply uses table scan operator to return all rows.įigure 2: Disjunctive predicates, query simplification and SC In this case, during the optimisation, QO simplifies the query by excluding all predicates knowing that A=A will always evaluate to true for all rows. The answer lies, again, in the way QO handles the query. This wouldn’t be possible if Name=98765 predicate evaluated first, due to conversion error. If the predicates switch the places, the query will still run with no errors. The successful execution of the query may lead us to believe that Sql Server uses minimal evaluation, but it’s not the case. However, if the conversion fails, the query will return error If the conversion succeed(like in the example) the query will execute with no errors. QO will then try to convert the column value(N’98765′) to INT and than to compare with the given argument(98765). On the other hand, if the operator finds the row, the first predicate will be evaluated (Name=98765). The first expression is shown in the Predicate section of the execution plan only for consistency purpose. If the Seek operator does not find clustered N’HA!’ the WHERE filter evaluates to false making the first expression redundant. QO decides to “push” second predicate ( CurrencyId = N’HA!’e) down to the query tree to the Index Seek data access operator making it “Seek Predicate”. Successful query: Query optimiser knows that the second expression, CurrencyId = N’HA!’ includes Primary Key constraint on the column(enforced by an unique clustered index) and therefore can evaluate to true maximum once. If we ran the same query without the second expression the query would fail due to conversion error. Switching the predicate places will have no effect to the QO’s reasoning. Conversion failed when converting the nvarchar value 'Australian Dollar' to data type int.*/įigure 1: Conjunctive predicates – second expression evaluated first