Viewing 15 posts - 3,241 through 3,255 (of 7,614 total)
Somewhat confusing, but I think this may return the rows you want:
SELECT T.*, Z.*
FROM
#TEMP1 T
INNER JOIN
[TSI].[ZATS_BROKER_FEED] Z
ON T.Part_Num...
July 30, 2018 at 9:43 am
Non-clustered index(es) are almost always a waste of resources on a staging table.
A clustered index is much more likely to be useful, although it's obviously not guaranteed to...
July 30, 2018 at 8:19 am
You don't really need a cursor for what you're described.
DECLARE @job_name_pattern nvarchar(128)
DECLARE @sql nvarchar(max)
SET @job_name_pattern = 'MyJobEvery%'
SELECT @sql = CAST((
July 27, 2018 at 10:24 am
July 25, 2018 at 12:46 pm
set statistics io,time off
DROP TABLE latestrecords ;
GO
CREATE TABLE latestrecords
(
Id int,
Email varchar(200),
Customer_FirstName varchar(200),
Status varchar(200),
RecordTimestamp DATETIME
)
GO
July 24, 2018 at 1:22 pm
July 24, 2018 at 12:53 pm
July 24, 2018 at 12:42 pm
July 24, 2018 at 11:32 am
July 24, 2018 at 11:17 am
The imperfect index definition is a drag on the first query, requiring a sort of all rows. Correcting the index definition:
DROP INDEX IX_latestrecords_1 ON latestrecords;
CREATE UNIQUE INDEX...
July 24, 2018 at 10:50 am
Not enough details to get specific, but in very general terms, I would likely go with a new option.
Keep the existing tables to do the current logging, but...
July 23, 2018 at 2:21 pm
Consider using system views such as sys.dm_db_index_operational_stats. Presumably you know at least the db(s) in which the code operates, although hopefully object names as well (or at least most...
July 20, 2018 at 8:02 am
Viewing 15 posts - 3,241 through 3,255 (of 7,614 total)