Viewing 15 posts - 1,516 through 1,530 (of 2,883 total)
Heh, I wouldn't say I am "smarter", I would say "I got lucky". I took mrsiro's approach and just expanded on it. A bad (or possibly good?) habit of mine...
September 18, 2020 at 2:47 pm
I half agree with Jeff there. Python may not be the best option for all use cases but, like cursors, there are cases where it is the best or only...
September 18, 2020 at 2:36 pm
My opinion - I don't think there are that many use cases for using it. Similar to R - you can access it externally, does it need to be baked...
September 17, 2020 at 8:47 pm
Possibly not the most efficient approach, but I think this should work:
SELECT
[job3].[TheDate]
, REPLACE( [job3].[Security]
, 'REMOVE:'
, ''
) AS [Security]
, REPLACE( [job3].[Driver]
, 'REMOVE:'
, ''
...
September 17, 2020 at 8:40 pm
Are you updating the tables sequentially or are some being done at the same time?
That being said, how many rows are being updated in tbl_people? If on 2020-08-07 it updated...
September 17, 2020 at 7:41 pm
My opinion - I would use it when I need to do analytics on the data; similar to when you'd use R.
My approach though is to use these tools outside...
September 17, 2020 at 7:30 pm
Alternately to Sue's approach, try matching your SSMS version to your SQL Server engine version. I know some things behave strangely when you have mismatched versions.
September 17, 2020 at 6:04 pm
It could be the disks. It could be the data. It could be the CPU or memory. It could be blocking. It could be none of those. It could be...
September 17, 2020 at 2:11 pm
I think this script will do it:
USE [msdb];
GO
SELECT
[name]
, [step_id]
, [step_name]
, [message]
, [run_status]
, [run_date]
, [run_time]
, [run_duration]
FROM[dbo].[sysjobhistory]
JOIN[dbo].[sysjobs]
ON [sysjobs].[job_id] = [sysjobhistory].[job_id]
WHERE[step_id] > 0;
Just add an extra...
September 16, 2020 at 7:35 pm
My advice - check the dump. Chances are it was not a specific query that caused the dump but something else. Could be a driver issue, could be hardware failure,...
September 16, 2020 at 7:05 pm
The issue is that NULL is an unknown value. @x=NULL and NOT(@x=NULL) both give a result of FALSE. Technically, they give NULL which gets evaluated to FALSE in a CASE...
September 16, 2020 at 5:54 pm
You can read it from another location, but you may be missing the symbol libraries. If possible, it is best to do it on the server that had the problem...
September 16, 2020 at 5:32 pm
As a thought, it may not hurt to reach out to the creators of "Relativity" to see what they recommend. Often the creators of the tool will have some good...
September 16, 2020 at 4:54 pm
That is a fun one with NULLs. The problem is that @x=@tempX can be true or false when either of those is NULL. Doing a comparison on if @x=NULL or...
September 16, 2020 at 4:40 pm
Pretty sure SQL has no built in way to monitor and alert for stack dumps.
This link has a powershell script for it though:
https://www.sqltechnet.com/2014/04/monitor-and-alert-sql-stack-dumps.html
September 16, 2020 at 4:27 pm
Viewing 15 posts - 1,516 through 1,530 (of 2,883 total)