Viewing 15 posts - 5,821 through 5,835 (of 59,089 total)
Hi, Still kind of a newbie to SQL Server. Anyway I have two tables: tblStaging and tblWorking. The staging table is updated every 15 minutes and I need to...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2021 at 10:35 pm
If you actually need a sequence, then we have a CREATE SEQUENCE statement in the language I need to just generate a set of integers then I would use
SELECT...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2021 at 9:56 pm
To be sure, I don't see any temporal queries in section 2.1... just the construct for your million row table.
Section 2.2 has a couple of temporal queries where you use...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2021 at 8:47 pm
how often have you needed to generate a sequence that started with something other than "1" or "0"?
I guess about every time when I wanted a sequence of something...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 3, 2021 at 8:04 pm
We differ in opinion only on whether or not using the Bulk Logged or Simple Recovery Model would be a "Pyrrhic victory" victory or not. I'm simply not...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2021 at 5:10 pm
p.s. Just in case there's a question about where I stand on this, I DO absolutely agree that taking a dif backup before and after Minimally logged rebuild should be...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2021 at 4:05 pm
I could be wrong but, from your description, it seems to me that you've not identified what the I/O contention is being caused by, yet. I/O contention is usually a...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2021 at 3:23 pm
Those are really good questions, Scott. First, I agree that the differentials are a great idea whether you're in the BULK LOGGED or SIMPLE Recovery Models. Better to be safe...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2021 at 3:06 pm
That's not true, Scott. The log can be applied. You just have to use the whole thing. You can't stop in the middle for a PIT restore. If something happens...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 2, 2021 at 3:43 am
If you were to simply rename the actual .SQLPLAN as a .TXT file, you'd probably get more takers because most won't want to unzip a file. They don't mind renaming...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2021 at 7:07 pm
Curious... what is the datatype for Col4?
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2021 at 7:05 pm
Even if the db is not normally in SIMPLE mode, you would certainly want it to be in SIMPLE for these rebuilds, to drastically reduce logging requirements.
If...
--Jeff Moden
Change is inevitable... Change for the better is not.
January 1, 2021 at 6:36 pm
If you have fragmented indexes and you make the mistake of doing index maintenance on indexes with a "0" or "100" Fill Factor (they're both the same), you will suffer...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2020 at 10:26 pm
I appreciate the unabridged version of the code but, like I asked above and on your previous post about this code, I see absolutely no reason at all for this...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 31, 2020 at 7:25 pm
With a table that large, say you have a total of 6 indexes, 1 clus and 5 nonclus.
I'd expect it to be faster to do a REBUILD ALL...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 30, 2020 at 11:08 pm
Viewing 15 posts - 5,821 through 5,835 (of 59,089 total)