09:00 - 19:0019:00 - 00:00
I have 2 queries deadlocking on each other.
The first query is
Select Top 1 NULL From [Table1] with (HOLDLOCK, TABLOCKX)
Second Query is an insert query that only reads from [Table2] to put data into [Table3]
The first query somehow has an exclusive lock on Table2 and tries to grab an exclus...
I would start by verifying the integrity of the data. Then, I would send any rejected rows to a file. You can specify this in your COPY command:
COPY CSI.MKT_RSRCH_AGG_ALL
FROM '/opt/vertica/CSI/MKT_RSRCH_AGG_ALL.txt'
DELIMITER '|'
NULL ''
REJECTED DATA '/path/to/rejected/data'
DIRECT;
Docu...
I got several notifications from The Heap that should have targeted another user.
The notification link to chat is:
http://chat.stackexchange.com/transcript/message/15284325?noredirect=1#15284325
It should have notified this user: http://chat.stackexchange.com/users/115579/max
I imagine the ...
This is a known issue. There have been some attempts to fix the problem, but they're not foolproof. See these:
Stack Exchange chat name mention inbox confusion
Getting Marc's chat notifications
What are the rules for when chat messages appear in a user's inbox?
CREATE PROC udploop
(
@num varchar(10)
)
AS
BEGIN
DECLARE @len int;
SET @len = LEN(@num);
WHILE (@len > 1)
BEGIN
SELECT @num = RIGHT(@num, @len - 1) ;
PRINT @num;
SET @len = @len;
END
END
4679
679
79
9
3390
390
90
0
9906
906
06
6
EXEC:
EXEC udploop 34679
EXEC udploop 13390
EXEC ...
18
In order to increase the efficiency with which poor quality questions are closed, it could make sense to have weighted close votes for a small subset of qualified users.
A very good way to measure the qualified users would be to leverage the tag badges. However, it needs to be rationally limite...
I'm not sure what to call a query that... isn't really a query; is "statement" a better word to use in place? Or how about "script"?
Or would something else be more appropriate?
Note: I've seen someone call it a "DELETE query" once
As a person's commitment to the community increases, I think we should make it possible for high-reputation users to fast-track the closure of certain questions. My reasons are many; for brevity, I won't repeat them all in detail here. But you can find them in all of the recent discussions here...09:00 - 19:0019:00 - 00:00
