See how one of the leading financial services organizations uses Recorded Future as part of a holistic threat intelligence program to promote security awareness and proactively and efficiently identify threats.
This has 4,938 rows, consuming 9.461 MB.
CREATE TABLE [dbo].[Integrations_Queue]( [QueueID] [bigint] IDENTITY(1,1) NOT NULL, [IntegrationID] [tinyint] NULL, [RecID] [bigint] NULL, [QueuedAt] [smalldatetime] NULL, [SubmittedAt] [smalldatetime] NULL, [IsError] [tinyint] NULL, [XMLData] [varchar](max) NULL, CONSTRAINT [PK_Integrations_Queue] PRIMARY KEY CLUSTERED ( [QueueID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY] GO
If I clear out most of the rows, delete the index, re-add the index, all is well until I get back up to a higher number of rows. If I simply rebuild the index, or even reorganize (even to the point that it has nearly 0% fragmentation), it will still take several minutes on an update query. And it's not even the index that's really the issue I don't think - I just issued a query a while ago after archiving 4,800 records into a different table - the following query took > 10 minutes to delete all 4,832 rows:
UPDATE Integrations_Queue SET SubmittedAt=GETUTCDATE(), IsError=0 WHERE QueueID=23923
DELETE FROM Integrations_Queue WHERE SubmittedAt IS NOT NULL AND IsError=0
SELECT * FROM Integrations_Queue WHERE QueueID=28723
|statistics before and after huge DEL/INS||3||16|
|How can I get this "NOT IN" to work?||5||17|
|Determine next b-weekly date||12||56|
|Writing a function to counts the number of primes in the range [1-N].||4||29|
Join the community of 500,000 technology professionals and ask your questions.
Connect with top rated Experts
21 Experts available now in Live!