Viewing 15 posts - 8,206 through 8,220 (of 59,091 total)
Hi Lowell,
I execute as follow
insert into [dbo].[master_profile]([profile_name], [profile_ic_no])
select [NAMA], [NOKP_NEW]
from [dbo].[EMPMAS_DATA]
insert into [dbo].[master_individual]([profile_id], [identification_no])
select
MyLookup.profile_ic_no,
MySource.[NOKP_NEW]
from [dbo].[EMPMAS_DATA] MySource
INNER JOIN [dbo].[master_profile]...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:57 pm
Explosive growth of TempDB is normally caused by just one thing... some code that has created a many-to-many join, accidentally or not. To emphasize the problem with this, let's call...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:51 pm
Heh... like I said, I even said to immediately regrow it to 2GB in my first post on the subject. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:42 pm
I'm with Jeff on your analysis, but not on his suggestion on tackling the Transaction Log (not completely, at least!)
I'd still go with the shrink the size to 0...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:30 pm
Worth reading about Netflix and the Chaos Monkey approach
Do you have any links? (or did I simply miss them in the article?)
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:03 pm
Thanks, Jeff!
I completely understand your rationale for shrinking the log file to 0 for the reasons you mentioned, but let me ask—in your experience, how resource intensive is the...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 2:00 pm
IMHO, your analysis is spot on, Mike. You only need to decide on what the growth of each file should be in MB.
Since the Log file did grow by 10%...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 4:52 am
Thank you for your reply! That is very helpful 🙂 I need to run this purge job once a week but unfortunately I don't know how many rows it...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 4:36 am
Our annual DiRT testing takes place this weekend. We're not Google by any means but it's just as important to us. The whole company gets involved in one form or...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 5, 2019 at 4:16 am
Jeff Moden wrote:Exactly and well said. And if someone keeps in mind that there will almost always be...
2.A better answer...
Especially with my code :-/
Heh... so say we all about our...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 10:08 pm
Sam, I hope you didn't miss the following because that SHRINK FILE stuff isn't going to solve your slow deletes.
https://www.sqlservercentral.com/forums/topic/slow-deletes#post-3704281
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 9:44 pm
jeff- you just made me laugh out loud and spill my tea all over my new keyboard about job security. I was chatting to a guy I work with...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 9:40 pm
Yes. I tried the shrinkfile but it doesnt release free space which is around 500MB. I dont know why!!
Ok... I'm humbled. NICE CALL MIKE!!! 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 9:38 pm
I wonder whether I will be cast out from The Thread as a maverick grammar nutjob for suggesting that NSO would be a better abbreviation, given that 'verbal' means...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 9:29 pm
We combine OPENQUERY against a LinkedServer and it does appear to help performance quite a bit (especially when pointing at AS400s or IBM PowerSystems). I have no measured stats...
--Jeff Moden
Change is inevitable... Change for the better is not.
December 4, 2019 at 4:49 pm
Viewing 15 posts - 8,206 through 8,220 (of 59,091 total)