Viewing 15 posts - 3,841 through 3,855 (of 6,041 total)
robin.pryor (5/26/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 1:23 pm
Luis Cazares (5/26/2015)
Eric M Russell (5/26/2015)
A simple CAST operation from date/time to date won't necessarily prevent usage of an index on a date/time column. For example, given the following table...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 11:33 am
I'm not understanding your usage of that WHERE clause.
The syntax for a joined update is basically the following:
UPDATE A
SET ..
FROM A
JOIN B ..
WHERE ..
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 11:27 am
You can also reference scalar user defined functions within check constraints.
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 11:03 am
Confirm there is not a trigger on this table, or some other change data capture mechanism, that inserts into an audit table for which the datatype of Age is still...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 11:00 am
Lynn Pettis (5/26/2015)
itortu (5/26/2015)
SELECT orderno
FROM _order
WHERE CAST(FLOOR(CAST(order_date AS FLOAT)) AS DATETIME)
BETWEEN CAST('5/14/2015' AS DATETIME)
AND CAST('5/15/2015' AS DATETIME)
ORDER BY order_date asc
The...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 10:51 am
Kyrilluk (5/26/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 10:30 am
robin.pryor (5/26/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 9:58 am
Wayne West (5/25/2015)
Ross McMicken (5/25/2015)
GPO (5/23/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 26, 2015 at 8:01 am
Gary Varga (5/22/2015)
Eric M Russell (5/22/2015)
Gary Varga (5/22/2015)
Eric M Russell (5/22/2015)
T_Peters (5/21/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 22, 2015 at 10:03 am
Gary Varga (5/22/2015)
Eric M Russell (5/22/2015)
T_Peters (5/21/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 22, 2015 at 8:03 am
The high level data flow depends on the sequence for which the application calls the stored procedures, so perhaps ask the application team if they have a diagram. Also, running...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 22, 2015 at 7:34 am
mrl6254 (5/21/2015)
I have been told that numerous applications each today with their own database...
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 22, 2015 at 7:14 am
T_Peters (5/21/2015)
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 22, 2015 at 6:44 am
If you feel confident that this particular query should always leverage the non-clustered columnstore index, then have you tried an index like so?
WITH (INDEX (IX_EmployeeReview_CS))
"Do not seek to follow in the footsteps of the wise. Instead, seek what they sought." - Matsuo Basho
May 21, 2015 at 11:52 am
Viewing 15 posts - 3,841 through 3,855 (of 6,041 total)