Viewing 15 posts - 9,406 through 9,420 (of 59,102 total)
Thanks all once again.. How can I attach the execution plan
Ya know... since they've updated this forum to new software, that's a really good question. I hope they fix...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2019 at 12:20 pm
Apologies... it took longer to find than expected.
The following code makes up to 450 possible substitutions. Details are in the code. Please understand that I've not tested the method I...
--Jeff Moden
Change is inevitable... Change for the better is not.
May 1, 2019 at 12:59 am
Heh... wrong color... it needs to be a Red Herring to chop down trees with. 😀
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 10:44 pm
The NULLs for EACH ROW are actually stored in the Row Header of EACH ROW and, as of 2012, is always stored for every column even if the column is...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 9:15 pm
If you work for an organization that counts lines code as a metric for developer productivity, then RedGate's "SQL Prompt" extension for SSMS is a great investment. A poorly...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 1:45 pm
To be honest, there's something wrong with such people's mentality. As a good online friend of mine once said, "It's probably 'cuz their mommas didn't know how to cook with...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 1:38 pm
I agree with the others about using the "Divide'n'Conquer" method. The only thing is that if the output of these views is massive, you could end up having some problems...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 1:27 pm
Thanks! I was able to solve this by taking database offline then immediately bringing it back online.
This sounds like the storage (SAN/mountpoint?) where the LOG file was...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 30, 2019 at 1:07 pm
Thanks. I've got to find some old code I wrote for fixing street addresses that did (IIRC) 400 replacements. I'll look for it after work tonight.
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 11:11 pm
I think the reason why you've gotten no help is because you've not provided any readily consumable data. Please see the link in my signature below for one way to...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 10:53 pm
I've used this and it certainly wasn't overkill. The client had a lot of resources on the SQL Server, but the main database was highly transactional, and performed very...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 10:46 pm
So how did you fix the issue? And when did the issue occur? After a restart or what?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 10:39 pm
How many possible rows are going to be in the Search/Replace values table?
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 10:36 pm
Thom A, I could imagine your suggestion might result in better performance if large offsets are added (or subtracted) from a date. However the function was designed for an...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 10:31 pm
Thanks for your suggestions and sorry about delay of reply - have been out of office for a couple of days/ Unfortunately, as good as they are, the suggestions...
--Jeff Moden
Change is inevitable... Change for the better is not.
April 29, 2019 at 1:28 pm
Viewing 15 posts - 9,406 through 9,420 (of 59,102 total)