Viewing 15 posts - 8,671 through 8,685 (of 59,072 total)
For those that may be following this thread...
Mike provided the results for the code I asked for in a PM. He didn't want to reveal monthly counts, drive letters, etc,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2019 at 7:31 pm
@ Briceston,
Please see the first link in my signature line below for why Erland is saying what most of us are thinking. We try to help a lot of people...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2019 at 2:54 pm
Gents,
First, thank you all for chiming in with the provided insight.
I have since upgraded to SQL Server 2017 for those who mentioned the usage of the older SQL Server...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 8, 2019 at 2:27 am
@ Briceston,
Considering the brief interlude between Erland and myself as well as Scott's previous early warning, do you have another column that could act as a temporal tie-breaker? For example...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2019 at 9:45 pm
On SQL 2012 and later:
WITH CTE AS (
SELECT AccountNumber, TxtAmount, PrevAmount = LAG(TxnAmount) OVER (PARTITION BY AccountNumber ORDER BY TransactionDate), TransactionDate
...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2019 at 9:34 pm
BWAAA-HAAAAA!!!!... I thought you said you had "a lot to think about". 😀 I didn't know you were going to jump right in and do it even on a dev...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2019 at 9:26 pm
Jeff: Thanks for pointing out dbgaragedays's post; I skipped right over it.
To be sure, I meant it as a compliment to the both of you. The two posts serve...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 7, 2019 at 12:10 am
Sam,
what will the following command return?
exec sp_spaceused 'dbo.CONTROL_HIST'It looks like you have BLOB data types, however I don't see it in the table definition.
With all the...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2019 at 2:22 pm
Why do you have to write all the script components? I thought SSIS was supposed to make it so you basically wouldn't have to write anything.
I don't know...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2019 at 12:34 pm
Just an FYI - but everything that batch files does can be done in SSIS.
For FTP/sFTP - you can use WinSCP and a script component to download files.
For ZIP...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2019 at 11:41 am
Jeff,
Would it help to split the table into 2. One with all data except the varchar(max) and one with the same ID and the varchar(max) only?
Mike
Exactly BUT... you don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 6, 2019 at 1:02 am
Rather than check the table, I check the main index on the table to see how many rows it has. In my experience, this is much faster than checking...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2019 at 2:06 am
If you run it a million times. In this case here the OP has no 'from' clause so it only executes once. I actually did read your article a...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2019 at 1:55 am
Sorry. I should withdraw that comment, at least temporarily.
The article (Script actually) has not been released for publication - i posted it just today.
Ah... got it. Nah... don't withdraw...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 5, 2019 at 1:13 am
That's a pretty strong indication that the problem may exist. All of those items are actually in the Clustered Index. With the large row count and the fact that "only"...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 4, 2019 at 10:12 pm
Viewing 15 posts - 8,671 through 8,685 (of 59,072 total)