Viewing 15 posts - 15,316 through 15,330 (of 59,063 total)
I've found that fragmentation has nothing to do with deadlocks. Neither does the optimizer even consider fragmentation when determining what the execution plan should look like.
More likely, it's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 8:14 pm
Shifting gears a bit, you've basically posted the same question different ways for the same problem 3 times now. Here are the other two. --Jeff Moden Change is inevitable... Change for the better is not.
https://www.sqlservercentral.com/Forums/1866664/Tlog-backups-indicate-no-data-change
https://www.sqlservercentral.com/Forums/1865369/Migrating-Databases-from-old-version-to-new-version-in-shortest-time
RBAR is pronounced "ree-bar" and is a "Modenism" for Row-By-Agonizing-Row.
First step towards the paradigm shift of writing Set Based code:
________Stop thinking about what you want to do to a ROW... think, instead, of what you want to do to a COLUMN.
Helpful Links:
How to post code problems
How to Post Performance Problems
Create a Tally Function (fnTally)
March 25, 2017 at 7:55 pm
Didn't see this article when it was first published. Job well done! Thanks for taking the time to write it up!
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 7:44 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 7:43 pm
I also recommend that you stop using quoted identifiers for aliases and that you make the resulting datatype for the THEN and ELSE be the same so that you don't...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 7:06 pm
I don't have any links to anything specific but I can tell you a bit from personal experience. I don't know what format your external sources are in but every...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 6:56 pm
To repeat what I said on your near duplicate post on this topic...
My recommendation stands as it did on the other thread.
1. I assume you're...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 6:34 pm
My recommendation stands as it did on the other thread.
1. I assume you're doing normal full backups at the very least. If they're not being done daily, that's...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 6:26 pm
Heh... "DevOps Specialist". IMHO, that should be the poster-child word example for "oxymoron". 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 25, 2017 at 4:04 pm
Nothing to do with the article... I'm just really happy that I don't work for a company with 15 development teams and 100+ developers. 😉
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 4:46 pm
For the db backup restore project moving ~ 1200 dbs ( some vldbs 500 GB...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 4:32 pm
i need to update 1500 employee records,
my new data i have in Excel,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 4:29 pm
I've found that working from home on a dedicated project allows me to get a whole lot more done... if I ignore the company email, urgent PMs, text messages, etc,...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 4:10 pm
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 3:56 pm
I have files that come in everyday that needs to be bulk inserted. Some...
--Jeff Moden
Change is inevitable... Change for the better is not.
March 24, 2017 at 3:42 pm
Viewing 15 posts - 15,316 through 15,330 (of 59,063 total)