Viewing 15 posts - 19,696 through 19,710 (of 59,072 total)
JoseMenendez (8/29/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2015 at 3:23 pm
Conversations like this strike me in an odd way. If there's a performance problem, the first thing people do is blame the database and if it takes more than...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2015 at 2:25 pm
and not exists (select * from ContractorCoverageException cce where cce.contractorcoverageid = a.id and postalid = postal.id)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2015 at 1:50 pm
Doing a much deeper dive on everything that you've presented so far and being a bit of a troubleshooter, I'm having a logical problem with a point or two on...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2015 at 1:00 pm
coolchaitu (8/30/2015)
I did not rebuild ALL indexes in the database with fillfactor=90. Only on some tables, index fragmentation was greater than 95%. For these indexes, i rebuilt with...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 30, 2015 at 10:10 am
Thanks for the answers. It's kinda late tonight but I'll build a shedload of data tomorrow based on your answers and we'll dive into indexes and use of clustered...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 9:27 pm
KGJ-Dev (8/29/2015)
Hi Jeff , thanks for the reply and yes, the dump table has 3 million same kind of data. I also mentioned in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 4:07 pm
ScottPletcher (8/29/2015)
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:51 pm
I'll also add that, for the example given, I see no need for the script table at all. The only thing that's changing is a value in the WHERE...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:46 pm
You could use INSERT/EXECUTE (requires the precreation of the table to store the results of the stored procedure in) or you could use sanitized inputs to create a dynamic call...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:41 pm
andrewbb (8/29/2015)
Is it possible hackers deliberately marketed non-SP solutions to make hacking easier?
If the code built in the managed code is properly parameterized instead of consisting of concatenated dynamic SQL,...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:37 pm
coolchaitu (8/29/2015)
I reduced the fill factor value, set it to 90 and then rebuilded the indexes. It worked for majority of indexes. However, for some...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:34 pm
In the process of considering a clustered index, you can't just consider SELECTs. You also have to consider page splits during inserts and updates and many other factors like...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 3:00 pm
Except for two foreign key errors (you can't put FK's on Temp Tables), your attached code ran up to the final SELECT to the display as you posted it in...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 1:36 pm
diegosiao (8/28/2015)
People who don't really know much about databases are the ones that frequently suggest the approach...
--Jeff Moden
Change is inevitable... Change for the better is not.
August 29, 2015 at 12:58 pm
Viewing 15 posts - 19,696 through 19,710 (of 59,072 total)