Viewing 15 posts - 1,111 through 1,125 (of 2,905 total)
I would probably take this approach (although not that efficient, it is easy to read in my opinion):
where (p.JCCo=@Company and p.Job=@Job and substring(Phase,1,3) not in (' 00','... June 15, 2021 at 5:39 pm
I agree with Steve's view on this one. I'd also like to add that SSL encryption is VERY fast and it only encrypts data in motion. Websites using HTTPS is...
June 14, 2021 at 8:09 pm
Did a quick google on this and found this link:
https://stackoverflow.com/questions/18996157/what-does-lock-communication-buffer-resources-mean
From what I am understanding from the above, the communication buffer in a deadlock means that there were multiple parallel processes...
June 14, 2021 at 7:44 pm
I agree with ZZartin and even have a sample script that replicates this behavior:
CREATE TABLE #tmpTable (id INT)
GO
SET STATISTICS IO ON
INSERT INTO [#tmpTable]
(
[id]
)
VALUES
(
0-- id - int
)
INSERT INTO...
June 14, 2021 at 7:21 pm
There are a few things I'd check.
In no particular order:
I'd try to create a new job, run it, and see if it logs the job history. It could be something...
June 14, 2021 at 7:09 pm
ok, so step 1 from what I had was to get all of the job status's within the timeframe. The query you have handles that, but I'd pull out some...
June 14, 2021 at 5:37 pm
That approach works if you are storing it in a table. Just add that as a column to the table.
June 11, 2021 at 10:03 pm
It depends entirely on the approach you want to take and how you are planning on storing the data permanently.
Is this data going into a table or is it generated...
June 11, 2021 at 9:36 pm
As for generating a checksum, this is entirely possible, but it depends on how you want to handle it and what you plan to do with it.
If I understand the...
June 11, 2021 at 9:14 pm
First thing I'd be curious about is with the wait stats for PAGEIOLATCH_SH being over 2 million, is that for that one job OR since the instance started?
Quick google on...
June 11, 2021 at 7:33 pm
Sorry, my query had a typo in it - I missed giving the quantifier for the part number in the CTE.
This one should work better:
DECLARE @MaskChar CHAR(1)...
June 11, 2021 at 6:22 pm
It is definitely possible, but does become more challenging based on what you have in your original query. What would probably be easier would be something more like this:
June 11, 2021 at 4:37 pm
I expect that auto-scaling would make the AWS space grow, but it shouldn't make TEMPDB grow past the limits you put in place.
June 11, 2021 at 3:53 pm
Does this work:
SELECT
[finalDatapc].[familyid]
, [finalDatapc].[PartNumber]
, [finalDatapcMask].[MaskNumber]
FROM[getfinaldatapc] AS [finalDatapc]
JOIN[getfinaldatapcmask] AS [finalDatapcMask]
ON [finalDatapcMask].[familyid] = [finalDatapc].[familyid]
AND
(
LEFT([finalDatapc].[PartNumber], LEN([finalDatapc].[PartNumber]) - 1) = LEFT([finalDatapcMask].[MaskNumber], LEN([finalDatapcMask].[MaskNumber]) - 1)
AND RIGHT([finalDatapc].[PartNumber], 1)NOT LIKE...
June 11, 2021 at 3:49 pm
Are you able to capture the execution plan for these? That could help determine what is actually happening. Do the queries run just as slow if you run them in...
June 11, 2021 at 3:30 pm
Viewing 15 posts - 1,111 through 1,125 (of 2,905 total)