Viewing 15 posts - 8,656 through 8,670 (of 59,091 total)
I'll also state that if you have the UNIQUE index you say you do as...
-- PK or unique key is combined key(custid,procustid,team_id)
... we'd not be able to build the sample...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2019 at 6:37 pm
I work best in an environment that has a constant background noise like a 20" box fan (good source of the right tone of "pink" noise for me) to drown...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2019 at 3:59 pm
He can supply it - just needs to use SQL Sentry Plan explorer to anonymize it before posting here.
The thing is... he doesn't actually need to supply it because...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2019 at 2:26 am
I agree that the procedure need to be fixed but coming to terms with 120 TB being processed is very perflxing(how a RAM of 196 GB is processing 120...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 15, 2019 at 2:14 am
Is the index in question a "Clustered Index"?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 14, 2019 at 10:02 pm
Hi, the tables are updated using SSIS package basically what happens is an sql command runs (delete from table) then a connection to an external odbc dbase (Select *...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2019 at 1:32 pm
Hi Folks, a general question here for better admin on a database. Have a number of tables, with approx 100 rows that clear down and re-populate every 5 minutes,...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2019 at 12:54 pm
Hmmm... I wonder if the new Cardinality Estimator would actually do a better job at this?
--Jeff Moden
Change is inevitable... Change for the better is not.
September 12, 2019 at 12:30 pm
Wow, Patrick. You totally missed the point. Ron stated that Gail said something that she didn't actually say and that was the point of contention.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 11:09 pm
Thank you both for looking at this. Another spanking for me by SQL Server - what else is new? But it's not going to be that much work to...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 7:48 pm
I assume that the EXISTS operator must be pushing down a row estimate because all it takes is a single match and EXISTS stops executing. So instead of hash...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 7:46 pm
she then concludes that these results should all but put the nail in the coffin on integers vs naturals keys. This is NOT a valid conclusion...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 6:33 pm
It must not like you... I tried the same thing and got no such error. I'm using FireFox. You might want to let them know which browser you're using.
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 6:25 pm
Looking at the "Plain" version of the execution plans, it would appear that the IF EXISTS is trivializing the the estimated row counts to <2 in most cases. That is...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 6:17 pm
The real underlying problem here is that you're trying to filter on an aggregated (XML concatenation IS a form of aggregation) column, which is never a good idea and is...
--Jeff Moden
Change is inevitable... Change for the better is not.
September 11, 2019 at 3:35 pm
Viewing 15 posts - 8,656 through 8,670 (of 59,091 total)