Viewing 15 posts - 16 through 30 (of 7,413 total)
It should be more efficient to do that using a trigger rather than doing a separate UPDATE after the load. The trigger would also allow for indirect notification (you wouldn't...
March 25, 2024 at 6:32 pm
I would think one UPDATE -- with the IN condition added -- would be much better than 3 separate UPDATEs, since the main table will then only have to be...
March 20, 2024 at 9:15 pm
Typically EXISTS / NOT EXISTS is most efficient when it's a viable option.
You'll want to have a (nonclus) index on B ( AppId, NotificationDate ). If the table already has...
March 20, 2024 at 7:16 pm
Agree with Phil, that's a critical q.
Also, efficiency will depend on the indexes on the tables. You'll need to be able to review indexes.
March 20, 2024 at 5:43 pm
Try these and see if they help. Be sure to review the query plan to verify:
INDEX ON mq: ( TABLE_NAME, ROWID_MQ_DATA_CHANGE )
UPDATE mq
SET mq.sent_state_id = 6,
UPDATED_BY =...
March 20, 2024 at 1:45 pm
It would be simpler and more efficient to just calc the 3rd Friday of the month and then see if there are any rows for that date, i.e., you don't...
March 19, 2024 at 5:57 am
I don't see why you'd need more then 150GB of RAM for a 31GB table. If that's "the big table" in the db, presumably the entire is only 50 or...
March 17, 2024 at 3:59 am
Agreed. You really want to have all the dbs having the same owner.
March 15, 2024 at 8:58 pm
We would need DDL for the tables and some cardinality info (how many rows for each condition).
But, overall, IF that is a consistent query pattern, you should cluster the table...
March 14, 2024 at 3:02 pm
I prefer the 2nd approach, but for the 1st approach:
The processed_flag should be a bit, 0/1, rather than a full char (y/n). If you already have a bit column(s) in...
March 12, 2024 at 3:37 pm
Need sample data that is directly usable, that is, CREATE TABLE and INSERT statement(s), not just a splat on the screen.
March 8, 2024 at 9:57 pm
D'OH, sorry, that should be:
CAST(GETDATE() AS date)
March 8, 2024 at 2:06 pm
You've already got restrictions based on @LOOK_BACK_PERIOD in the WHEREs, it would just be more efficient to pre-filter rather than waiting until some processing has been done on all the...
March 7, 2024 at 8:41 pm
Did you add the WHERE condition for the TXN_DATE? If you have a long history in the table, that would help the most.
Then try an index on (txn_date, company) include...
March 7, 2024 at 6:17 pm
Viewing 15 posts - 16 through 30 (of 7,413 total)